The origin draft only was discussing SCHC as an IP Protocol Number.
At IETF115, the attendees agreed that the draft needs to be expanded to
also SCHC as an Ethertype and as a UDP Port Number.
Thus the old draft name no longer reflects the new content. There is a
mechanism when you submit a draft to link it to a prior draft so the
draft history is properly maintained (it does not support linking to
multiple prior drafts or splitting an old draft into multiple, for that
you have to ask for human help).
So the new draft name will reflect the new draft content.
I just don't have enough time to get content into the new draft prior to
Passover Holiday start. I hope to get it done during the middle days,
say Sunday. Stay tuned. Pascal Thubert is helping me with the new
content. Particularly the specific content needed to liason with IEEE
802 on the Ethertype.
Bob
On 4/5/23 11:49, tom petch wrote:
From: Int-area <int-area-boun...@ietf.org> on behalf of Robert Moskowitz
<rgm-i...@htt-consult.com>
Sent: 05 April 2023 12:22
I am in the process of reving draft
draft-ietf-intarea-schc-ip-protocol-number
and adding support for schc as an ethertype and tcp/udp port number as I
said I would do back in Nov. Sigh.
So what to name the new draft?
<tp>
If you are producing a new version of
draft-ietf-intarea-schc-ip-protocol-number-00 then I would call it
draft-ietf-intarea-schc-ip-protocol-number-01. I do not see any other logical
choice.
Tom Petch
draft-ietf-intarea-schc-protocol-numbers
??
Alternatives?
Thanks and now back to my writing as I really want to get an update out
today before Holidays...
Bob
_______________________________________________
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
