Dear Paul and Scott, I merged the input from Paul on which bits should be encoded for the gponGemPti IE.
https://author-tools.ietf.org/diff?doc_1=draft-netana-opsawg-ipfix-gpon-gem-00&url_2=https://raw.githubusercontent.com/network-analytics/draft-netana-opsawg-ipfix-gpon-gem/refs/heads/main/draft-netana-opsawg-ipfix-gpon-gem-01.txt I understood that both of you wanted to reach out to the ITU-T wherever there is an existing GEM PTI (Section 8.3.1 G.984.3) registry where an IPFIX subregistry (https://www.iana.org/assignments/ipfix/ipfix.xhtml) could refer to. We like at the IPFIX IANA managed registry to avoid duplication wherever possible since later they will be hard to manage. The ITU-T registry should be machine readable since there are IPFIX data collection implementations (https://mailarchive.ietf.org/arch/msg/opsawg/cgxHtKqO9Yks7wSFXr5HGDI0yUE/) which obtain the IPFIX definitions from the IANA registry automatically. Let me know wherever you had any feedback and wherever I can help in anyway like establishing a liaison between ITU-T and OPSAWG/CCAMP. Best wishes Thomas -----Original Message----- From: Graf Thomas, INI-NET-VNC-E2E Sent: Thursday, April 10, 2025 12:45 PM To: Aitken, Paul <[email protected]>; [email protected] Subject: RE: draft-netana-opsawg-ipfix-gpon-gem-00 Dear Paul, That's very much appreciated. srhFlagsIPv6 is a good example which refers to https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#segment-routing-header-flags. If that would not be possible we would need to re-create the registry as in dataLinkFrameType and refer to the ITU-T document. The challenge I see is that all ITU-T documents are listed here: https://www.itu.int/rec/T-REC-G/en and for G.984.3 here https://www.itu.int/rec/T-REC-G/recommendation.asp?lang=en&parent=T-REC-G.984.3, but I wasn't able to find a registry. I will raise this today at the CCAMP interim and feedback when I have infos. Best wishes Thomas -----Original Message----- From: Aitken, Paul <[email protected]> Sent: Thursday, April 10, 2025 10:43 AM To: Graf Thomas, INI-NET-VNC-E2E <[email protected]>; [email protected] Subject: Re: draft-netana-opsawg-ipfix-gpon-gem-00 Be aware: This is an external email. Thomas, I agree that it's good to avoid duplicate registries. The IE definition could point directly to the corresponding ITU definitions. Even better, we could create a new IPFIX sub-registry which points to the ITU definition. In either case the definition should clearly say whether it's intended to only use the ITU definition at the the time of publication, or to follow all future updates. eg, if one of the Reserved values is defined in future. This could be the first time for such an IPFIX definition (where the full details are external to the registry), so I've asked IANA for their advice. P. On 09/04/25 06:16, [email protected] wrote: > Dear Paul, > > Thanks for the review. Well spotted. I will consolidate the terminology in > section 2 once the document is mature and complete. > > I will extend the description in both IE's describing that the first 3 resp. > 12 bits are being used. > > Section 8.3.1 of > https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-G.984.3-201401-I!!PDF-E&type=items > defines the PTI registry. I like to avoid that we are replicating this in > IPFIX so that we have to maintain two registries. Would it be ok if I > describe under Additional Information where the registry is? What is your > recommendation? > > Best wishes > Thomas > > -----Original Message----- > From: Aitken, Paul <[email protected]> > Sent: Tuesday, April 8, 2025 9:14 PM > To: [email protected] > Subject: draft-netana-opsawg-ipfix-gpon-gem-00 > > > Be aware: This is an external email. > > > > In section 2 the terminology can be reduced as many of those terms are not > used elsewhere in the document. > > In section 5.1.1. please describe how the 3 bits are encoded into the > unsigned8: which of the 8 bits are used, and what is the ordering? > > Likewise in section 5.1.2. please describe how the 12 bits are encoded into > the unsigned16. > > Thanks, > P.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
