On 9/7/22 12:56, Joel Halpern wrote:
From your description, it seems clear that the SCHC header is not an
extension header. It does not follow the rules for extension
headers. Instead, it is an upper layer / carried protocol, just like
IP in IP, or UDP carrying all sorts of interesting network layer headers.
I should clarify, that the Next Header value is almost always there, but
just not in the physically in the datagram.
It could even be UDP with a rule that squeezes it down to zero bytes on
the wire. Further, since this is the ONLY SCHC rule between the 2
parties, the physical length of the SCHC rule is also zero. So what you
may actually see on the wire is SCHC as Protocol Number and the next
byte is the CID of a DTLS header.
So how do you label this thing?
Bob M.
Yours,
Joel
On 9/7/2022 12:47 PM, Robert Moskowitz wrote:
On 9/7/22 12:36, Bob Hinden wrote:
Pascal,
On Sep 6, 2022, at 11:26 PM, Pascal Thubert (pthubert)
<pthubert=40cisco....@dmarc.ietf.org> wrote:
Hello Bob M.
My support remains, and so does my earlier comment. I believe the
IANA section should indicate that the IPv6 extension header type
registry must be also updated, see the notes at the top of
https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
Is this an IPv6 extension header? Does SCHC include a next header
field so it can point to a header that follows?
I think it does (at least in some cases), but wanted to confirm
this. Might be good to add a few words in the draft that describes
this.
Oh, boy....
That is all compressed! The SCHC rule may say to expand and put in
the next header.
For example the content is ESP, which it self is compressed according
to appropriate SCHC rules.
So no, there is probably never an explicit Next Header.
And yes, there is almost always, after expansion, a header to be
processed.
Wierd....
Bob M.
Bob
All the best;
Pascal
From: Int-area <int-area-boun...@ietf.org> On Behalf Of Robert
Moskowitz
Sent: mercredi 7 septembre 2022 4:44
To: Internet Area <int-area@ietf.org>
Subject: [Int-area] Resubmit - requesting WG Adoption
draft-moskowitz-intarea-schc-ip-protocol-number
As was discussed at the INTAREA meeting at IETF 114,
I request that a call for WG adoption of this draft.
I have made draft name change and edits per Bob Hinden.
As I said earlier, there is a lot of work which will cascade in
other areas once this is one its way.
thanks
Bob
-------- Forwarded Message --------
Subject:
New Version Notification for
draft-moskowitz-intarea-schc-ip-protocol-number-00.txt
Date:
Tue, 06 Sep 2022 19:40:41 -0700
From:
internet-dra...@ietf.org
To:
Stuart W. Card <stu.c...@axenterprize.com>, Adam Wiethuechter
<adam.wiethuech...@axenterprize.com>, Robert Moskowitz
<r...@labs.htt-consult.com>, Stuart Card <stu.c...@axenterprize.com>
A new version of I-D,
draft-moskowitz-intarea-schc-ip-protocol-number-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-intarea-schc-ip-protocol-number
Revision: 00
Title: Internet Protocol Number for SCHC
Document date: 2022-09-06
Group: Individual Submission
Pages: 7
URL:
https://www.ietf.org/archive/id/draft-moskowitz-intarea-schc-ip-protocol-number-00.txt
Status:
https://datatracker.ietf.org/doc/draft-moskowitz-intarea-schc-ip-protocol-number/
Html:
https://www.ietf.org/archive/id/draft-moskowitz-intarea-schc-ip-protocol-number-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-moskowitz-intarea-schc-ip-protocol-number
Abstract:
This document requests an Internet Protocol Number assignment for
SCHC so that SCHC can be used for IP independent SCHC of other
transports such as UDP and ESP.
The IETF Secretariat
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
