From: Stephen Hemminger <stephen@networkplumber.org>
To: marcel@holtmann.org, gustavo@padovan.org, johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Fw: [Bug 195269] New: Bluetooth - 6lowpan -- RFC7668 vs. draft - IPv6 addressing
Date: Thu, 6 Apr 2017 17:19:41 -0400 [thread overview]
Message-ID: <20170406171941.2fe9e3d0@plumbers-lap.home.lan> (raw)
Any bugzilla entries networking related ends up (forwarding to MAINTAINERS)
Begin forwarded message:
Date: Thu, 06 Apr 2017 11:37:40 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 195269] New: Bluetooth - 6lowpan -- RFC7668 vs. draft - IPv6 addressing
https://bugzilla.kernel.org/show_bug.cgi?id=195269
Bug ID: 195269
Summary: Bluetooth - 6lowpan -- RFC7668 vs. draft - IPv6
addressing
Product: Networking
Version: 2.5
Kernel Version: 4.9.0-2-amd64 (Debian)
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: aignerb@technikum-wien.at
Regression: No
Dear all,
my first bug report (hopefully :-)) for the Kernel ^^
Citing 6lowpan.c:675:
/* Universal/local bit set, BT 6lowpan draft ch. 3.2.1 */
If the address is identified as a public address, the original address byte
get's a set bit at 2^1.
Otherwise, it will be deleted.
so far, so good. That works well, BUT:
the current RFC7668 does NOT state anything like that. Neither in ch. 3.2.1 or
any other chapters I looked through.
Please tell me, am I wrong or is this a non-conform implementation?
Anyway, thank you very much for this rock-stable piece of software :-)
Best wishes, Benjamin
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-04-06 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170406171941.2fe9e3d0@plumbers-lap.home.lan \
--to=stephen@networkplumber.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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