Hello again Benjamin:
Just to make sure you're kept busy ; )
> > Proposed changes in 3.5. Primary and Secondary 6BBRs
> >
> > "
> >A Registering Node MAY register the same address to more than one
> >6BBR, in which case the Registering Node uses the same EARO in all
> >the parallel
Hello Benjamin:
Let's go then!
> >
> > So I suggest 'typically' instead of "if needed":
> > "
> >Typically, Node A starts with an uncompressed packet and compacts the
> >IPv6 packet using the header compression mechanism defined in
> >[RFC6282].
> > "
>
> That seems reasonable.
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over Networks of Resource-constrained
Nodes WG of the IETF.
Title : On Forwarding 6LoWPAN Fragments over a Multihop IPv6
Network
Authors :
Hello again Benjamin:
I published -15
https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-minimal-fragment-15 with the
changes.
I kept the Datagram_Tag uppercased but we can debate that with the RFC editor.
The lowercase is used in RFC 4944.
Looking at the diffs, I found that I forgot to remove
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over Networks of Resource-constrained
Nodes WG of the IETF.
Title : IPv6 Backbone Router
Authors : Pascal Thubert
Mirja Kühlewind has entered the following ballot position for
draft-ietf-6lo-fragment-recovery-20: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Hello again, Benjamin
> > Again and again, many thanks for your arch-fantastic reviews!
> > "
> > Each Backbone Router (6BBR) maintains a data structure for its
> >Registered Addresses called a Binding Table. The abstract data that
> >is stored in the Binding Table includes the
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over Networks of Resource-constrained
Nodes WG of the IETF.
Title : 6LoWPAN Selective Fragment Recovery
Author : Pascal Thubert
Hello Again Mirja : )
> Thanks for this additional text. I just cleared my discuss.
Very cool; again and again, many thanks for your deep reviews.
>
> A couple of nits you/Suresh maybe want to add as RFC editor note:
Happy to republish:
The IESG has approved the following document:
- 'On Forwarding 6LoWPAN Fragments over a Multihop IPv6 Network'
(draft-ietf-6lo-minimal-fragment-15.txt) as Proposed Standard
This document is the product of the IPv6 over Networks of
Resource-constrained Nodes Working Group.
The IESG contact
Hi Pascal,
I went through the latest rev and found an off-by-one error on the Fragment
size.
* Section 5.1.
Fragment_Size: 10-bit unsigned integer; the size of this fragment in
a unit that depends on the Link-Layer technology. Unless
overridden by a more specific
On Mon, Mar 23, 2020 at 10:17:43AM +, Pascal Thubert (pthubert) wrote:
> Hello again Benjamin:
>
> Just to make sure you're kept busy ; )
>
> > > Proposed changes in 3.5. Primary and Secondary 6BBRs
> > >
> > > "
> > >A Registering Node MAY register the same address to more than one
> >
12 matches
Mail list logo
