Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
Fred, IANA has enough code points for SCHC over IP/Ethernet/UDP and for OMNI (NDP code point if I remember correctly). I.e., this not one or the other. And SCHC early allocation (if any) won't block/prevent any other allocations. Moreover, per RFC 7120 section 2 point d) d. The Working Group chairs and Area Directors (ADs) judge that there is sufficient interest in the community for early (pre-RFC) implementation and deployment, or that failure to make an early allocation might lead to contention for the code point in the field. I.e., early allocation will be done for adopted documents where there is a clear interest. Hope this clarifies Regards, -éric From: Int-area on behalf of "Templin (US), Fred L" Date: Wednesday, 9 November 2022 at 16:11 To: "Juan Carlos Zuniga (juzuniga)" , "int-area@ietf.org" Subject: Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00 I want to understand whether granting these allocations for SCHC would prevent OMNI from receiving exactly the same three allocation types. If so, then we need to ask the question of whether the codepoints should go to SCHC or OMNI. In my view, OMNI should get the codepoints. Fred From: Int-area On Behalf Of Juan Carlos Zuniga (juzuniga) Sent: Wednesday, November 09, 2022 8:07 AM To: int-area@ietf.org Subject: [EXTERNAL] [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00 EXT email: be mindful of links/attachments. 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 numbers. Once we have that draft published, we will re-confirm our call for adoption, and then we will proceed to coordinate with tsvwg as discussed. Best, Juan-Carlos & Wassim (IntArea chairs) ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
Re: [Int-area] About draft-templin-intarea-parcels
On Wed, Nov 9, 2022 at 7:47 AM Templin (US), Fred L wrote: > > Richard, thank you for your message. The intarea community must understand > that > > the live IP Parcels presentation given today was only a “roadmap” to a proper > > presentation which could not be given due to time constraints. The charts > shown > > during the live presentation were skipped over quickly, but they provide full > > detail and are permanently available here: > > > > > https://datatracker.ietf.org/meeting/115/materials/slides-115-intarea-ip-parcels > > > > Running code is also now permanently available here: > > > > https://github.com/fltemplin/ip-parcels > > > > and provides clear evidence that IP parcels provide an appreciable performance > > gain which cannot be ignored any longer. > > > > IP parcels are good for the Internet, and the presentation charts and running > code > > provide clear evidence. It is time to adopt IP parcels. Fred, Thanks for the data and implementation, but I'm still not convinced that IP parcels should be adopted. Your data seems to show that when the networking stack processes large segments performance increases (fewer packets to process in the data path is a win). We've known this for a long time and that's why stacks commonly implement various segmentation techniques like GSO/TSO, GRO/LRO, UFO, USO, and more recently BigTCP. Also, within the data center, 9K MTUs are becoming common place which is even better than segmentation with 1500 byte MTU. The major difference between these techniques and IP parcels is that the segmentation techniques don't require any new protocol or changes to an existing protocol, whereas IP parcels requires protocol changes. So in order to justify IP parcels adoption, not just in IETF but also upstreaming into Linux, I think you'll want to show that it has significant benefits over the existing segmentation techniques to justify the complexities and cost of a new protocol. Tom > > > > Fred > > > > From: Int-area On Behalf Of Richard Li > Sent: Wednesday, November 09, 2022 6:12 AM > To: int-area@ietf.org > Subject: [Int-area] About draft-templin-intarea-parcels > > > > Hi Chairs and All, > > > > At today’s intarea meeting, the chair asked the participants if anybody has > an interest in this draft or not. If nobody is interested, this draft will be > closed, and if anyone is interested, he/she is asked to voice it on the > mailing list. > > > > As a follow up, I am expressing my interest in this draft, and would like to > see this draft open and let it go on. A few months ago, I asked its authors > several questions, and the authors answered and clarified them. I do see good > values for some use cases, especially for those in broadband access and jumbo > frames being used on the links. It seems to me that this draft points to a > useful direction, some rooms are remaining for expansion though. > > > > Thanks, > > > > Richard > > > > ___ > 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
Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
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 numbers. Working on it :) Once we have that draft published, we will re-confirm our call for adoption, and then we will proceed to coordinate with tsvwg as discussed. Best, Juan-Carlos & Wassim (IntArea chairs) ___ 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
Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
I want to understand whether granting these allocations for SCHC would prevent OMNI from receiving exactly the same three allocation types. If so, then we need to ask the question of whether the codepoints should go to SCHC or OMNI. In my view, OMNI should get the codepoints. Fred From: Int-area On Behalf Of Juan Carlos Zuniga (juzuniga) Sent: Wednesday, November 09, 2022 8:07 AM To: int-area@ietf.org Subject: [EXTERNAL] [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00 EXT email: be mindful of links/attachments. 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 numbers. Once we have that draft published, we will re-confirm our call for adoption, and then we will proceed to coordinate with tsvwg as discussed. Best, Juan-Carlos & Wassim (IntArea chairs) ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
[Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
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 numbers. Once we have that draft published, we will re-confirm our call for adoption, and then we will proceed to coordinate with tsvwg as discussed. Best, Juan-Carlos & Wassim (IntArea chairs) ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
Re: [Int-area] About draft-templin-intarea-parcels
Richard, thank you for your message. The intarea community must understand that the live IP Parcels presentation given today was only a “roadmap” to a proper presentation which could not be given due to time constraints. The charts shown during the live presentation were skipped over quickly, but they provide full detail and are permanently available here: https://datatracker.ietf.org/meeting/115/materials/slides-115-intarea-ip-parcels Running code is also now permanently available here: https://github.com/fltemplin/ip-parcels and provides clear evidence that IP parcels provide an appreciable performance gain which cannot be ignored any longer. IP parcels are good for the Internet, and the presentation charts and running code provide clear evidence. It is time to adopt IP parcels. Fred From: Int-area On Behalf Of Richard Li Sent: Wednesday, November 09, 2022 6:12 AM To: int-area@ietf.org Subject: [Int-area] About draft-templin-intarea-parcels Hi Chairs and All, At today’s intarea meeting, the chair asked the participants if anybody has an interest in this draft or not. If nobody is interested, this draft will be closed, and if anyone is interested, he/she is asked to voice it on the mailing list. As a follow up, I am expressing my interest in this draft, and would like to see this draft open and let it go on. A few months ago, I asked its authors several questions, and the authors answered and clarified them. I do see good values for some use cases, especially for those in broadband access and jumbo frames being used on the links. It seems to me that this draft points to a useful direction, some rooms are remaining for expansion though. Thanks, Richard ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
[Int-area] eBPF standardization side meeting
In the ARTAREA and INTAREA meetings, I gave an announcement about the eBPF side meeting on Thursday. Time: 6pm London time Duration: 1 hour Zoom: https://us06web.zoom.us/j/83038515863?pwd=czQrWTdVcGlMWER2MGN6V2pOSFhGQT09 In person room: Mezzanine 12 The eBPF Foundation has entertained four possibilities for where to do eBPF cross-platform documentation: 1. Published by eBPF Foundation 2. Published by eBPF Foundation and then taken to ISO to get an ISO number assigned 3. Published as Independent Stream RFC(s) 4. Published as IETF RFC(s) The purpose of the side meeting is to discuss which path is most appropriate. If you have views on where, please come to the side meeting. Dave ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
[Int-area] About draft-templin-intarea-parcels
Hi Chairs and All, At today's intarea meeting, the chair asked the participants if anybody has an interest in this draft or not. If nobody is interested, this draft will be closed, and if anyone is interested, he/she is asked to voice it on the mailing list. As a follow up, I am expressing my interest in this draft, and would like to see this draft open and let it go on. A few months ago, I asked its authors several questions, and the authors answered and clarified them. I do see good values for some use cases, especially for those in broadband access and jumbo frames being used on the links. It seems to me that this draft points to a useful direction, some rooms are remaining for expansion though. Thanks, Richard ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
