Re: [IPFIX] BBF WT-352
PJ Aitken <[email protected]> Mon, 16 Jan 2017 21:38:52 +0000
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
--===============4351683536866251308== Content-Type: multipart/alternative; boundary="------------0ED5743D68068DDEE68AC988" --------------0ED5743D68068DDEE68AC988 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit Marta, it's good to hear that you're thinking of using some IPFIX Information Elements. The latest IPFIX elements are in IANA's registry. You can contact [email protected] to discuss and review new proposals. The formal request for new elements is usually made 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 > Protocol (ICTP) for NGPON2 (Next Generation Passive Optical Networks) > protocol. We have been discussing in WT-352 the use of IPFIX as a > unicast stream protocol for transporting the following data elements > across NGPON2 Channel Terminations (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-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 NGPON2 vendors. > > RFC 7013 provides guidance to authors interested in expanding IANA > registry (for Flow applications) and the existence of IPFIX doctors. > RFC 7013 provides guidance for those interested in expanding IANA > registries. What I would 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://urldefense.proofpoint.com/v2/url?u=http-3A__www.iana.org_assignments_ipfix_ipfix.xhtml&d=DwMFAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=bDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=2VPV6V0iOc6sir2gtzZxjFfUZUnFnDatfeUfeEppBm4&e=> > (is this the most up to date registry) > > 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 > contact with respect to this? > > Regards, > > Marta Seda > > > > _______________________________________________ > IPFIX mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipfix&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=bDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=vf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9wtGKGbdqcWjk&e= --------------0ED5743D68068DDEE68AC988 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Marta, it's good to hear 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 class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> to discuss and review new proposals. The formal request for new elements is usually made either in an RFC or through a request to IANA.<br> <br> P.<br> <br> <br> <div class="moz-cite-prefix">On 15/01/17 21:18, Marta Seda wrote:<br> </div> <blockquote cite="mid:BY2PR0501MB173436984FCA8FD98EA3DE009C7A0@BY2PR0501MB1734.namprd05.prod.outlook.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @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:Times; panose-1:2 2 6 3 5 4 5 2 3 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} 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;} 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;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;} @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 67698713 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 67698691 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;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext="edit" spidmax="1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]--> <div class="WordSection1"> <p class="MsoNormal">Hello,<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">I am the editor of Broadband Forum WT-352 Inter-Channel Termination Protocol (ICTP) for NGPON2 (Next Generation Passive Optical Networks) protocol. We have been discussing in WT-352 the use of IPFIX as a unicast stream protocol for transporting the following data elements across NGPON2 Channel Terminations (CTs):<o:p></o:p></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l1 level1 lfo1"> <!--[if !supportLists]--><span style="font-family:Symbol;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">dhcp leases<o:p></o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l1 level1 lfo1"> <!--[if !supportLists]--><span style="font-family:Symbol;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">pppoe session information<o:p></o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l1 level1 lfo1"> <!--[if !supportLists]--><span style="font-family:Symbol;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">Igmp data (e.g., channel, uptime, etc)<o:p></o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l1 level1 lfo1"> <!--[if !supportLists]--><span style="font-family:Symbol;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">ARP data <o:p> </o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l1 level1 lfo1"> <!--[if !supportLists]--><span style="font-family:Symbol;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">OMCI ME instance (optional)<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN">Any bidirectional TLVs are transported using ICTP (not IPFIX).<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN">We are proposing to reuse some IANA TLVs for WT-352 (rather 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 NGPON2 vendors.<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN">RFC 7013 provides guidance to authors interested in expanding IANA registry (for Flow applications) and the existence of IPFIX doctors. RFC 7013 provides guidance for those interested in expanding IANA registries. What I would like to understand is the following:<o:p></o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2"> <!--[if !supportLists]--><span style="font-family:"Calibri",sans-serif;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">A)<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">Where can BBF pull the latest (or in progress) IPFIX IE? I have been using: <a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.iana.org_assignments_ipfix_ipfix.xhtml&d=DwMFAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=bDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=2VPV6V0iOc6sir2gtzZxjFfUZUnFnDatfeUfeEppBm4&e=">http://www.iana.org/assignments/ipfix/ipfix.xhtml</a> (is this the most up to date registry)<o:p></o:p></span></p> <p class="MsoListParagraph" style="text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2"> <!--[if !supportLists]--><span style="font-family:"Calibri",sans-serif;mso-fareast-language:ZH-CN"><span style="mso-list:Ignore">B)<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="mso-fareast-language:ZH-CN">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 contact with respect to this?<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN">Regards,<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN">Marta Seda<o:p></o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align:justify"><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p class="MsoNormal"><o:p> </o:p></p> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ IPFIX mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipfix&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=bDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=vf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9wtGKGbdqcWjk&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipfix&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=bDtxxCIPW_T3jeiYOQCvkKo800_8HuyXUPQHGVom_6E&s=vf4XRV9bB7AyXYDckfsLCtJ5IpdRwD9wtGKGbdqcWjk&e=</a> </pre> </blockquote> <br> </body> </html> --------------0ED5743D68068DDEE68AC988-- --===============4351683536866251308== 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 --===============4351683536866251308==--