Re: [IPFIX] BBF WT-352
Marta Seda <[email protected]> Wed, 25 Jan 2017 20:15:50 +0000
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <BY2PR0501MB1734F8A6008509D2EE63D7D39C740@BY2PR0501MB1734.namprd05.prod.outlook.com> |
--===============3454736197865891525== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BY2PR0501MB1734F8A6008509D2EE63D7D39C740BY2PR0501MB1734_" --_000_BY2PR0501MB1734F8A6008509D2EE63D7D39C740BY2PR0501MB1734_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thank you - P. I am including others at BBF in clarifications we need in W= T-352. I would like clarification on the following IANA Informational Elements: 1) minFlowStartSeconds: The earliest absolute timestamp of the first p= acket within any Flow within the scope containing this Information Element,= rounded down to the second if necessary. This Information Element SHOULD b= e bound to its containing IPFIX Transport Session via an options record and= the sessionScope Information Element. Q: Is this informational element specific to netflow? Could it be re-purp= osed for other purposes (e.g., the length of time a PPPoE session started)?= (if not supported in IANA, BBF can create one for WT-352 purposes) 2) dot1qVlanId: The value of the 12-bit VLAN Identifier portion of the= Tag Control Information field of an Ethernet frame. The structure and sem= antics within the Tag Control Information field are defined in [IEEE802.1Q Q: I guess this question is more about confirming this definition. In WT-= 352, we need to be able to identify the S-tag and C-tag. This definitions = seems to point to the S-tag. Is this the correct interpretation of the IAN= A IPFIX IE? 3) dot1qCustomerVlanId: The value represents the Customer VLAN identifi= er in the Customer field as described in IEEE802.1Q]. Q: This definitions seems to point to the C-tag. Is this the correct inte= rpretation of the IANA IPFIX IE? Appreciate your feedback. Regards, Marta From: PJ Aitken [mailto:[email protected]] Sent: Monday, January 16, 2017 1:39 PM To: Marta Seda <[email protected]> Cc: [email protected]; [email protected] Subject: Re: [IPFIX] BBF WT-352 Marta, it's good to hear that you're thinking of using some IPFIX Informati= on Elements. The latest IPFIX elements are in IANA's registry. You can contact [email protected]<mailto:[email protected]> to discuss = and review new proposals. The formal request for new elements is usually ma= de either in an RFC or through a request to IANA. P. On 15/01/17 21:18, Marta Seda wrote: Hello, I am the editor of Broadband Forum WT-352 Inter-Channel Termination Protoco= l (ICTP) for NGPON2 (Next Generation Passive Optical Networks) protocol. W= e have been discussing in WT-352 the use of IPFIX as a unicast stream proto= col for transporting the following data elements across NGPON2 Channel Term= inations (CTs): * dhcp leases * pppoe session information * Igmp data (e.g., channel, uptime, etc) * ARP data * OMCI ME instance (optional) Any bidirectional TLVs are transported using ICTP (not IPFIX). We are proposing to reuse some IANA TLVs for WT-352 (rather than re-inventi= ng new ones) and BBF introduce new TLVs not covered by IANA (e.g., NGPON2 s= pecific TLVs). WT-352 needs these TLVs to be defined for the purpose of in= teroperability among NGPON2 vendors. RFC 7013 provides guidance to authors interested in expanding IANA registry= (for Flow applications) and the existence of IPFIX doctors. RFC 7013 prov= ides guidance for those interested in expanding IANA registries. What I wo= uld like to understand is the following: A) Where can BBF pull the latest (or in progress) IPFIX IE? I have been= using: http://www.iana.org/assignments/ipfix/ipfix.xhtml<https://urldefens= e.proofpoint.com/v2/url?u=3Dhttp-3A__www.iana.org_assignments_ipfix_ipfix.x= html&d=3DDwMFAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1= TCoXNKhyPY8CFp8&m=3DbDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=3D2VPV6V0= iOc6sir2gtzZxjFfUZUnFnDatfeUfeEppBm4&e=3D> (is this the most up to date reg= istry) B) Would it be possible to have WT-352 proposed TLVs reviewed by IPFIX = doctors (to verify there is no overlap in definitions). Who could I contac= t with respect to this? Regards, Marta Seda _______________________________________________ IPFIX mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_ipfix&d=3DDwICAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729xYDYoCgBDdc= p1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DbDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&= s=3Dvf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9wtGKGbdqcWjk&e=3D --_000_BY2PR0501MB1734F8A6008509D2EE63D7D39C740BY2PR0501MB1734_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Helvetica; panose-1:2 11 6 4 2 2 2 2 2 4;} @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif; color:black;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New"; color:black;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman",serif; color:black;} p.msonormal0, li.msonormal0, div.msonormal0 {mso-style-name:msonormal; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman",serif; color:black;} span.EmailStyle19 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:windowtext;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:"Consolas",serif; color:black;} span.EmailStyle22 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:1544292670; mso-list-type:hybrid; mso-list-template-ids:71874216 39878840 67698713 67698715 67698703 6769871= 3 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-number-format:alpha-upper; mso-level-text:"%1\)"; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; mso-ascii-font-family:Calibri; mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri; mso-bidi-font-family:"Times New Roman";} @list l0:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level3 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l0:level4 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level5 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level6 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l0:level7 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level8 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level9 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l1 {mso-list-id:1626934067; mso-list-type:hybrid; mso-list-template-ids:-2008646266 67698689 67698691 67698693 67698689 6769= 8691 67698693 67698689 67698691 67698693;} @list l1:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l1:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l1:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l1:level4 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l1:level5 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l1:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l1:level7 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l1:level8 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l1:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l2 {mso-list-id:1798715831; mso-list-type:hybrid; mso-list-template-ids:-240477998 183170666 67698713 67698715 67698703 6769= 8713 67698715 67698703 67698713 67698715;} @list l2:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:11.0pt; font-family:"Times New Roman",serif; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; mso-bidi-font-family:"Times New Roman"; color:windowtext;} @list l2:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l2:level3 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l2:level4 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l2:level5 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l2:level6 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l2:level7 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l2:level8 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l2:level9 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l3 {mso-list-id:2055692756; mso-list-type:hybrid; mso-list-template-ids:-545980984 1775140710 67698713 67698715 67698703 676= 98713 67698715 67698703 67698713 67698715;} @list l3:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; color:black;} @list l3:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l3:level3 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l3:level4 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l3:level5 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l3:level6 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l3:level7 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l3:level8 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l3:level9 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body bgcolor=3D"white" lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"color:windowtext">Thank you – P= . I am including others at BBF in clarifications we need in WT-352.<o= :p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:windowtext"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"color:windowtext">I would like clarif= ication on the following IANA Informational Elements:<o:p></o:p></span></p> <p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level= 1 lfo5"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q= uot;Calibri",sans-serif;color:windowtext"><span style=3D"mso-list:Igno= re">1)<span style=3D"font:7.0pt "Times New Roman""> &n= bsp; </span></span></span><![endif]><span style=3D"font-family:"Calibri&quo= t;,sans-serif;color:windowtext">minFlowStartSeconds: </span><span style=3D"font-size:10.0pt;font-family:"Helvetica",sa= ns-serif">The earliest absolute timestamp of the first packet within any Fl= ow within the scope containing this Information Element, rounded down to th= e second if necessary. This Information Element SHOULD be bound to its containing IPFIX Transport Session via an options r= ecord and the sessionScope Information Element.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"He= lvetica",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 10.0pt;font-family:"Helvetica",sans-serif">Q: Is this infor= mational element specific to netflow? Could it be re-purposed for oth= er purposes (e.g., the length of time a PPPoE session started)? (if not supported in IANA, BBF can create one for WT-352 purposes)<o= :p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"He= lvetica",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoListParagraph" style=3D"margin-top:6.0pt;text-align:justify;= text-indent:-.25in;mso-list:l2 level1 lfo5"> <![if !supportLists]><span style=3D"font-size:11.0pt;font-family:"Cali= bri",sans-serif;color:windowtext"><span style=3D"mso-list:Ignore">2)<s= pan style=3D"font:7.0pt "Times New Roman""> &nbs= p; </span></span></span><![endif]>dot1qVlanId: The value of the 12-bit V= LAN Identifier portion of the Tag Control Information field of an Ethernet = frame. The structure and semantics within the Tag Control Information= field are defined in [IEEE802.1Q<span style=3D"color:windowtext"><o:p></o:= p></span></p> <p class=3D"MsoListParagraph" style=3D"margin-top:6.0pt;text-align:justify"= >Q: I guess this question is more about confirming this definition.&n= bsp; In WT-352, we need to be able to identify the S-tag and C-tag. T= his definitions seems to point to the S-tag. Is this the correct interpretation of the IANA IPFIX IE?<span style=3D"color:windo= wtext"><o:p></o:p></span></p> <p class=3D"MsoListParagraph" style=3D"margin-top:6.0pt;text-align:justify;= text-indent:-.25in;mso-list:l2 level1 lfo5"> <![if !supportLists]><span style=3D"font-size:11.0pt;font-family:"Cali= bri",sans-serif;color:windowtext"><span style=3D"mso-list:Ignore">3)<s= pan style=3D"font:7.0pt "Times New Roman""> &nbs= p; </span></span></span><![endif]>dot1qCustomerVlanId: The value represents th= e Customer VLAN identifier in the Customer field as described<span style=3D= "color:windowtext"><o:p></o:p></span></p> <p class=3D"MsoListParagraph" style=3D"mso-margin-top-alt:6.0pt;margin-righ= t:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;text-indent:.= 5in"> in IEEE802.1Q].<span style=3D"color:windowtext;mso-fareast-language:ZH-CN">= <o:p></o:p></span></p> <p class=3D"MsoListParagraph" style=3D"margin-top:6.0pt;text-align:justify"= ><span style=3D"font-family:"Calibri",sans-serif;color:windowtext= ">Q: </span> This definitions seems to point to the C-tag. Is this th= e correct interpretation of the IANA IPFIX IE?<span style=3D"color:windowte= xt"><o:p></o:p></span></p> <p class=3D"MsoListParagraph"><span style=3D"font-family:"Calibri"= ;,sans-serif;color:windowtext"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:windowtext">Appreciate your fee= dback. Regards,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:windowtext"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"color:windowtext">Marta<o:p></o:p></s= pan></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"color:windowtext">From:</span></b>= <span style=3D"color:windowtext"> PJ Aitken [mailto:[email protected]] <br> <b>Sent:</b> Monday, January 16, 2017 1:39 PM<br> <b>To:</b> Marta Seda <[email protected]><br> <b>Cc:</b> [email protected]; [email protected]<br> <b>Subject:</b> Re: [IPFIX] BBF WT-352<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Marta, it's good to h= ear that you're thinking of using some IPFIX Information Elements.<br> <br> The latest IPFIX elements are in IANA's registry.<br> <br> You can contact <a href=3D"mailto:[email protected]">[email protected]<= /a> to discuss and review new proposals. The formal request for new element= s is usually made either in an RFC or through a request to IANA.<br> <br> P.<br> <br> <span style=3D"font-size:12.0pt"><o:p></o:p></span></p> <div> <p class=3D"MsoNormal">On 15/01/17 21:18, Marta Seda wrote:<o:p></o:p></p> </div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <p class=3D"MsoNormal">Hello,<o:p></o:p></p> <p class=3D"MsoNormal"> <o:p></o:p></p> <p class=3D"MsoNormal">I am the editor of Broadband Forum WT-352 Inter-Chan= nel Termination Protocol (ICTP) for NGPON2 (Next Generation Passive Optical= Networks) protocol. We have been discussing in WT-352 the use of IPF= IX as a unicast stream protocol for transporting the following data elements across NGPON2 Channel Terminations (CTs):<o:p>= </o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l1 level1 lfo2"> <![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-= list:Ignore">·<span style=3D"font:7.0pt "Times New Roman""= > </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">d= hcp leases</span><o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l1 level1 lfo2"> <![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-= list:Ignore">·<span style=3D"font:7.0pt "Times New Roman""= > </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">p= ppoe session information</span><o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l1 level1 lfo2"> <![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-= list:Ignore">·<span style=3D"font:7.0pt "Times New Roman""= > </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">I= gmp data (e.g., channel, uptime, etc)</span><o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l1 level1 lfo2"> <![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-= list:Ignore">·<span style=3D"font:7.0pt "Times New Roman""= > </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">A= RP data </span> <o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l1 level1 lfo2"> <![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-= list:Ignore">·<span style=3D"font:7.0pt "Times New Roman""= > </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">O= MCI ME instance (optional)</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN">Any bidirectional TLVs are transported using ICTP (not = IPFIX).</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN">We are proposing to reuse some IANA TLVs for WT-352 (ra= ther than re-inventing new ones) and BBF introduce new TLVs not covered by = IANA (e.g., NGPON2 specific TLVs). WT-352 needs these TLVs to be defined for the purpose of interoperability among N= GPON2 vendors.</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN">RFC 7013 provides guidance to authors interested in exp= anding IANA registry (for Flow applications) and the existence of IPFIX doc= tors. RFC 7013 provides guidance for those interested in expanding IANA registries. What I would like to = understand is the following:</span><o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l0 level1 lfo4"> <![if !supportLists]><span style=3D"font-family:"Calibri",sans-se= rif"><span style=3D"mso-list:Ignore">A)<span style=3D"font:7.0pt "Time= s New Roman""> </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">W= here can BBF pull the latest (or in progress) IPFIX IE? I have been u= sing: <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.iana.o= rg_assignments_ipfix_ipfix.xhtml&d=3DDwMFAg&c=3DIL_XqQWOjubgfqINi2j= Tzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DbDtxxCIPW_T= 3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=3D2VPV6V0iOc6sir2gtzZxjFfUZUnFnDatfe= UfeEppBm4&e=3D"> http://www.iana.org/assignments/ipfix/ipfix.xhtml</a> (is this the most up = to date registry)</span><o:p></o:p></p> <p class=3D"MsoListParagraph" style=3D"text-align:justify;text-indent:-.25i= n;mso-list:l0 level1 lfo4"> <![if !supportLists]><span style=3D"font-family:"Calibri",sans-se= rif"><span style=3D"mso-list:Ignore">B)<span style=3D"font:7.0pt "Time= s New Roman""> </span></span></span><![endif]><span style=3D"mso-fareast-language:ZH-CN">W= ould it be possible to have WT-352 proposed TLVs reviewed by IPFIX doctors = (to verify there is no overlap in definitions). Who could I contact w= ith respect to this?</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN">Regards,</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN">Marta Seda</span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"mso-fare= ast-language:ZH-CN"> </span><o:p></o:p></p> <p class=3D"MsoNormal"> <o:p></o:p></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ti= mes New Roman",serif"><br> <br> <br> <o:p></o:p></span></p> <pre>_______________________________________________<o:p></o:p></pre> <pre>IPFIX mailing list<o:p></o:p></pre> <pre><a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></pre> <pre><a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.= ietf.org_mailman_listinfo_ipfix&d=3DDwICAg&c=3DIL_XqQWOjubgfqINi2jT= zg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DbDtxxCIPW_T3= jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=3Dvf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9wtGK= GbdqcWjk&e=3D">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__w= ww.ietf.org_mailman_listinfo_ipfix&d=3DDwICAg&c=3DIL_XqQWOjubgfqINi= 2jTzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DbDtxxCIPW= _T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=3Dvf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9w= tGKGbdqcWjk&e=3D</a> <o:p></o:p></pre> </blockquote> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ti= mes New Roman",serif"><o:p> </o:p></span></p> </div> </body> </html> --_000_BY2PR0501MB1734F8A6008509D2EE63D7D39C740BY2PR0501MB1734_-- --===============3454736197865891525== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix --===============3454736197865891525==--