linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, jukka.rissanen@linux.intel.com,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH bluetooth-next 2/4] 6lowpan: add nhc module for GHC extension header detection
Date: Wed, 25 Nov 2015 14:50:10 +0100	[thread overview]
Message-ID: <5655BC92.7050908@osg.samsung.com> (raw)
In-Reply-To: <20150918221429.GA12228@omega>

Hello.

On 19/09/15 00:14, Alexander Aring wrote:
> On Fri, Sep 18, 2015 at 11:44:15PM +0200, Alexander Aring wrote:
>> Hi,
>>
>> On Fri, Sep 18, 2015 at 01:52:46PM +0200, Stefan Schmidt wrote:
> ....
>
>> btw:
>>
>> Something is wrong at iana registration:
>>
>> https://www.iana.org/assignments/_6lowpan-parameters/_6lowpan-parameters.xhtml#lowpan_nhc
>>
>> For RFC6282 they did each entry for each extension header, for GHC not.
>>
>> Don't know why :-(
>>
>> Also iana says it's
>>
>> 10110EEN whereas RFC7400 says it's 1011EIDN
>>      ^
>>      |
>>      I don't know where this bit comes from.
>>
> it isn't wrong, GHC EID is defined for 0-3 only so the first bit is
> always zero. So 10110 E E N is right whereas:
>
> 1011000N -> Hop
> 1011001N -> Routing
> 1011010N -> Fragment
> 1011011N -> Destination
>
> Seems like Mobility and IPv6 is not defined for GHC.
>
> But I still don't know why iana put it for RFC6282 in a new entry on the
> list for each EID and for GHC they did only one entry for the mask without
> EID bits.

I guess we could ask them if we really want to know.

regards
Stefan Schmidt


  reply	other threads:[~2015-11-25 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 11:52 [PATCH bluetooth-next 0/4] GHC compression detection Stefan Schmidt
2015-09-18 11:52 ` [PATCH bluetooth-next 1/4] 6lowpan: clarify Kconfig entries for upcoming GHC support Stefan Schmidt
2015-09-18 11:52 ` [PATCH bluetooth-next 2/4] 6lowpan: add nhc module for GHC extension header detection Stefan Schmidt
2015-09-18 21:44   ` Alexander Aring
2015-09-18 22:14     ` Alexander Aring
2015-11-25 13:50       ` Stefan Schmidt [this message]
2015-11-25 13:50     ` Stefan Schmidt
2015-09-18 11:52 ` [PATCH bluetooth-next 3/4] 6lowpan: add nhc module for GHC UDP detection Stefan Schmidt
2015-09-18 21:50   ` Alexander Aring
2015-11-25 13:49     ` Stefan Schmidt
2015-09-18 11:52 ` [PATCH bluetooth-next 4/4] 6lowpan: add nhc module for GHC ICMPv6 detection Stefan Schmidt
2015-09-18 21:51   ` Alexander Aring
2015-11-25 13:50     ` Stefan Schmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5655BC92.7050908@osg.samsung.com \
    --to=stefan@osg.samsung.com \
    --cc=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).