On Wed, 21 Aug 2013, Brian E Carpenter wrote:
Hi Ron,
On 21/08/2013 01:33, Ronald Bonica wrote:
Hi Mike,
Thanks for your review of all three documents. The following is some gentle
pushback.
...
There is no real solution to the long header problem. The best
that we can do
Mike,
Good point! The pointer field in the ICMPv6 Parameter Problem Message needs to
carry some value.
My first guess would be to point at the first byte of the Fragment Header,
because the packet is improperly fragmented. I would not point at the Payload
Length in the IPv6 header, because
The reason I didn't suggest pointing at the Fragment Header is
because it would carry the same information that it would in a
correctly fragmented packet, namely M=1 and Fragment Offset=0 (the
signature of an initial fragment). The Payload Length field is what
indicates that the fragment is
The reason I didn't suggest pointing at the Fragment Header is
because it would carry the same information that it would in a
correctly fragmented packet, namely M=1 and Fragment Offset=0 (the
signature of an initial fragment). The Payload Length field is what
indicates that the fragment
: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
The reason I didn't suggest pointing at the Fragment Header is because
it would carry the same information that it would in a correctly
fragmented packet, namely M=1 and Fragment Offset=0 (the signature of
an initial fragment
: Wednesday, August 21, 2013 10:37 AM
To: C.M.Heard
Cc: IPv6
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
The reason I didn't suggest pointing at the Fragment Header is
because
it would carry the same information that it would in a correctly
fragmented packet
: Wednesday, August 21, 2013 10:37 AM
To: C.M.Heard
Cc: IPv6
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
The reason I didn't suggest pointing at the Fragment Header is
because
it would carry the same information that it would in a correctly
fragmented packet
...@ietf.org] On Behalf
Of Ole Troan
Sent: Wednesday, August 21, 2013 10:37 AM
To: C.M.Heard
Cc: IPv6
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
The reason I didn't suggest pointing at the Fragment Header is
because
it would carry the same information
Bonica
Cc: C.M.Heard; IPv6
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
This works, too. But now we have three participants in the discussion
and three opinions!
Let's just pick one! Does anybody have a coin?
who calls edge? ;-)
cheers,
Ole
Then 0 it is!
Ron
-Original Message-
From: C. M. Heard [mailto:he...@pobox.com]
Sent: Wednesday, August 21, 2013 12:01 PM
To: Ronald Bonica
Cc: Ole Troan; IPv6
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
Works for me.
//cmh
On Wed
] On Behalf Of
Ronald Bonica
Sent: Tuesday, August 20, 2013 9:34 AM
To: C. M. Heard; IPv6
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-oversized-header-chain-
04
Hi Mike,
Thanks for your review of all three documents. The following is some
gentle pushback.
At IETF 87, the 6man WG
To: IPv6
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-oversized-header-
chain-04
Greetings,
My main question is why this draft is not better integrated with
draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate,
which have overlapping or at least related subject matter
Greetings,
My main question is why this draft is not better integrated with
draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate,
which have overlapping or at least related subject matter.
The thrust of draft-ietf-6man-oversized-header-chain is to require
that all extension
Hi, Mike
On 08/19/2013 09:58 PM, C. M. Heard wrote:
My main question is why this draft is not better integrated with
draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate,
which have overlapping or at least related subject matter.
Because what's in
On 20/08/2013 16:02, Fernando Gont wrote:
Hi, Mike
On 08/19/2013 09:58 PM, C. M. Heard wrote:
My main question is why this draft is not better integrated with
draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate,
which have overlapping or at least related subject matter.
15 matches
Mail list logo
