G AGGFRAG encapsulation payload for ESP (TEMPORARY -
registered 2022-08-26,
document sent to IESG Evaluation 2022-07-14)
[draft-ietf-ipsecme-iptfs-18]
Suggest leaving this as just TBD.
Bob
On Sep 6, 2022, at 6:32 AM, Robert Moskowitz wrote:
As was discussed at
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 , Adam Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D
tools/submit barfs.
On 9/6/22 17:08, Bob Hinden wrote:
Bob,
inline
On Sep 6, 2022, at 10:06 AM, Robert Moskowitz wrote:
Bob H.,
thanks for the review!
I am using:
https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
For my source information.
I abbreviated "Int
changes.
But I hear you...
Bob
On 9/7/22 05:15, tom petch wrote:
From: Int-area on behalf of Robert Moskowitz
Sent: 07 September 2022 03:43
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
confirm before I add this.
Bob
All the best;
Pascal
*From:* Int-area *On Behalf Of *Robert
Moskowitz
*Sent:* mercredi 7 septembre 2022 4:44
*To:* Internet Area
*Subject:* [Int-area] Resubmit - requesting WG Adoption
draft-moskowitz-intarea-schc-ip-protocol-number
As was discussed
On 9/7/22 15:15, Carsten Bormann wrote:
On 2022-09-07, at 18:36, Bob Hinden wrote:
Is this an IPv6 extension header?Does SCHC include a next header field so
it can point to a header that follows?
If you haven’t seen RFC 5856 to 5858: This is a miniseries of documents where
we have
that there is
better understanding by non-SCHC conversant readers?
thanks
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)
wrote:
Hello Bob M.
My support remains, and so does my earlier
, 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
. Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-moskowitz-intarea-schc-ip-protocol-number-01.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-intarea-schc-ip-protocol-number
Revision: 01
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 On Behalf Of Robert Moskowitz
Sent: mercredi 7 septembre 2022 4:44
To: Internet Area
Subject: [Int-area] Resubmit - requesting WG Adoption
ader field. (AH does). But if we are going to pretend
that some headers are extensions headers and some are not, we should
try to be consistent with the description in 8200 (and 2460).
On 9/7/2022 4:57 PM, Robert Moskowitz wrote:
On 9/7/22 16:35, Carsten Bormann wrote:
On 7. Sep 2022, at
(AH does). But if we are going to pretend
that some headers are extensions headers and some are not, we should
try to be consistent with the description in 8200 (and 2460).
On 9/7/2022 4:57 PM, Robert Moskowitz wrote:
On 9/7/22 16:35, Carsten Bormann wrote:
On 7. Sep 2022, at 22:04, Bob Hin
On 9/7/22 16:35, Carsten Bormann wrote:
On 7. Sep 2022, at 22:04, Bob Hinden wrote:
To clarify my question, it only relates to if SCHC should be added to the IPv6
Extension Header Types registry. I continue to think that adding it to the IP
Protocol Number registry is fine.
I believe
H does). But if we are going to pretend
that some headers are extensions headers and some are not, we should
try to be consistent with the description in 8200 (and 2460).
On 9/7/2022 4:57 PM, Robert Moskowitz wrote:
On 9/7/22 16:35, Carsten Bormann wrote:
On 7. Sep 2022, at 22:04, Bob Hinde
going foreward.
thanks for your support.
Bob M.
Bob
On Sep 7, 2022, at 12:46 PM, Robert Moskowitz wrote:
On 9/7/22 15:15, Carsten Bormann wrote:
On 2022-09-07, at 18:36, Bob Hinden wrote:
Is this an IPv6 extension header?Does SCHC include a next header field so
it can point
Yes, adopt it then have the knockdown, drag out on WHAT is an Extention
Header...
Fun had by all!
On 9/7/22 16:55, Bob Hinden wrote:
Bob,
On Sep 7, 2022, at 1:53 PM, Robert Moskowitz wrote:
On 9/7/22 16:04, Bob Hinden wrote:
Bob,
To clarify my question, it only relates to if SCHC
On 9/7/22 19:08, Carsten Bormann wrote:
On 8. Sep 2022, at 00:05, Robert Moskowitz wrote:
But it is architecturally wrong to call what ROHC or SCHC as carrying an upper
layer protocol. They carry what is in our architecture a Transport Layer
protocol, acting in many ways as part of the IP
As was discussed at the INTAREA meeting at IETF 114,
I request that a call for WG adoption of this draft.
There is a lot of work which will cascade in other areas once this is
one its way.
I am open to draft name change. I really SHOULD have called it
something like:
On 9/8/22 08:31, Pascal Thubert (pthubert) wrote:
Hello Joel:
SCHC could be used to compress IP option headers and the residue be stored in a
SCHC option, which a next header points at uncompressed transport (e.g.,
encrypted, uncompressible).
Additionally, finding the SCHC context may
in
this discussion, what do you have in mind when you mention "
UDP-carrying headers-with-next-header as extension headers" ?
Thanks a lot for your clarifications,
Antoine Fressancourt
-Original Message-
From: Int-area On Behalf Of Joel Halpern
Sent: mercredi 7 septembre 2022
ither alternative.
Yours,
Joel
On 9/7/2022 6:05 PM, Robert Moskowitz wrote:
> It might be that the datagram can be interrogated for the Next Header
> and that MIGHT mean an update to 8200.
>
> AH, you can find the NH. ESP not, as it is in the encrypted par
Thanks Tom!
Wow is that buried... (IMHO)
The values seem to be all over the place. Any insight as to why this is?
Bob
On 9/8/22 11:55, tom petch wrote:
From: Int-area on behalf of Robert Moskowitz
Sent: 08 September 2022 14:03
On 9/8/22 08:31, Pascal Thubert (pthubert) wrote:
Hello
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-ietf-intarea-schc-ip-protocol-number-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-ietf-intarea-schc-ip-protocol-number
Revision: 00
Title: Internet Protocol Number for SCHC
On 9/30/22 05:20, Jens Finkhaeuser wrote:
Hi all,
since I found myself contributing to the draft, it should be obvious
that I'm interested in continuing.
I think the proposed steps make a lot of sense. It should be fairly
obvious that the distinction between identifiers and locators alone
der ranging solutions. If folks
haven’t
looked at them recently they probably should now (IP parcels too).
*From:*Int-area [mailto:int-area-boun...@ietf.org] *On Behalf Of
*Robert Moskowitz
*Sent:* Thursday, October 06, 2022 8:37 AM
*To:* Jens Finkhaeuser ; Luigi Iannone
*Cc:* int-area
*Subj
on and has no
meaning in these
discussions; the thing I work on which has meaning here is called:
“AERO”.
*From:*Robert Moskowitz [mailto:rgm-i...@htt-consult.com]
*Sent:* Thursday, October 06, 2022 1:42 PM
*To:* Templin (US), Fred L ; Jens
Finkhaeuser ; Luigi Iannone
*Cc:* int-area
Forwarded Message
Subject: New Version Notification for
draft-moskowitz-intarea-ipnumber-00.txt
Date: Fri, 05 Aug 2022 08:32:56 -0700
From: internet-dra...@ietf.org
To: Stuart W. Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-moskowitz
I just realized I should change the draft name to something like:
draft-moskowitz-intarea-schc-ipnumber
As this is not a draft for lpwan...
Next ver, or sooner if instructed.
On 8/5/22 11:36, Robert Moskowitz wrote:
Per comments at IETF114 in the LPWAN session, I have moved this draft
Since, in a sense, this is targetted at me to be the lab rat for this, I
will read all this over carefully to see what mess I am getting myself
into, :)
Bob
On 11/10/22 07:45, Bob Hinden wrote:
Don,
Adding a procedure describing how to obtain an Ethertype for IETF work seems
reasonable
Got dinner plans. :(
Only one kosher restaraunt in the area.
On 11/10/22 03:17, Luigi IANNONE wrote:
Hi All,
Hope you are having a great IETF week.
Just a small reminder for those that are interested in talking about
addressing, let’s meet 18h30 this evening @ registration desk.
Ciao
On 11/9/22 11:06, Juan Carlos Zuniga (juzuniga) wrote:
Hi IntArea WG,
Today we had an interesting discussion about the future of
draft-ietf-intarea-schc-ip-protocol-number-00.
We would like to ask Bob Moskowitz et al. to upload a revised I-D with
the text about the EtherType and UDP port
Sec 5.5: r/"proces "/"process "/
___
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
was added by others, primarily Pacal Thubert for
UDP firewall traversal. He will be providing the text for that use case.
Back to writing on this bumpy train ride...
Bob
On 4/6/23 00:13, to...@strayalpha.com wrote:
Hi, Bob,
On Apr 5, 2023, at 4:22 AM, Robert Moskowitz
wrote:
I am
—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com
On Apr 9, 2023, at 2:30 PM, Robert Moskowitz
wrote:
Joe,
My original use case was for SCHC as an IP Protocol Number with
diet-esp being the sample. WIthout this we have to do a hack on the
SPI management.
My more recent work
for
draft-ietf-intarea-schc-protocol-numbers-00.txt
Date: Mon, 10 Apr 2023 16:37:35 -0700
From: internet-dra...@ietf.org
To: Stuart W. Card , Adam Wiethuechter
, Pascal Thubert
, Robert Moskowitz ,
Stuart Card
A new version of I-D, draft-ietf-intarea-schc-protocol-numbers-00.txt
has
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?
draft-ietf-intarea-schc-protocol-numbers
??
Alternatives?
Thanks and
/5/23 11:49, tom petch wrote:
From: Int-area on behalf of Robert Moskowitz
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
Sameach!
Bob
On Apr 5, 2023, at 10:58 AM, Robert Moskowitz wrote:
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
-intarea-schc-protocol-numbers-02.txt
Date: Mon, 08 Apr 2024 12:57:09 -0700
From: internet-dra...@ietf.org
To: Stuart W. Card , Adam Wiethuechter
, Pascal Thubert
, Robert Moskowitz ,
Stuart Card
A new version of Internet-Draft
draft-ietf-intarea-schc-protocol-numbers-02.txt has been
Of *Robert
Moskowitz
*Sent:* Monday, April 08, 2024 1:01 PM
*To:* int-area
*Subject:* [EXTERNAL] [Int-area] Fwd: New Version Notification for
draft-ietf-intarea-schc-protocol-numbers-02.txt
Changed references for diet-esp to ipsecme workgroup.
Ahem, after I get through some working with students
40 matches
Mail list logo
