Re: [IPFIX] Search comments and feedbacks about the draft of IPFIX IE extension when considering BGP community

Benoit Claise <[email protected]> Wed, 20 Jul 2016 09:12:03 +0200
Newsgroups	gmane.ietf.ipfix
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============3737078665709395249==
Content-Type: multipart/alternative;
 boundary="------------8480352CD207A395A6CB4B71"

This is a multi-part message in MIME format.
--------------8480352CD207A395A6CB4B71
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

Dear all,

We know that the IANA considerations=20
<https://tools.ietf.org/html/rfc7012#section-7> mentions "expert review"=20
for the IPFIX registry <https://www.iana.org/assignments/ipfix/ipfix.xhtm=
l>.
This BGP community is actually a special IPFIX Information Element as=20
this is the first one based on RFC 6313=20
<https://tools.ietf.org/html/rfc6313>(basicList, subTemplateList,=20
subTemplateMultiList)
So it deserves special attention, review, and potential documentation as=20
its own RFC.

Regards, Benoit

> Hi, dear all.
>
> Nice meeting you in the mail-list of IPFIX. This IETF in Berlin right=20
> now, we submit a draft and present it about the IPFIX IE extension=20
> when considering BGP community. I=92m looking for comments and feedback=
s=20
> about our idea in new IE added in exporting the flow information=20
> correlated with BGP community. As dear chair told me that the=20
> mail-list is still alive, I follow the suggestion of putting my draft=20
> here and searching for advice and suggestions in the right place.
>
> Before that, I made a short summary of my draft which may be helpful=20
> in quick looking at the draft. When we consider traffic steering in=20
> our backbone network, we feel that the flow information based on BGP=20
> community is quite suitable. That=92s the reason why we write the draft=
.=20
> And we now recommend two IEs which may be assigned by IANA:=20
> bgpSourceCommunityList and bgpDestinationCommunityList.
>
> If you are facing up with this situations as us, then we can discuss=20
> about the IEs especially the details.
>
> The information of my draft:=20
> https://www.ietf.org/internet-drafts/draft-li-opsawg-ipfix-bgp-communit=
y-00.txt
>
> I=92m looking forward for your comments.
>
> Best regards and have a nice trip in Berlin.
>
> -----------------------------------------------------------
>
> Rong Gu
> China Mobile Research Institute
> No.32 Xuanwumen West Street, Xicheng District
> Beijing, China, 100053
> Mobile: +86 13811520541
> Phone: +86 10 15801696688 Ext. 36211
> Email: [email protected] <mailto:[email protected]>
>


--------------8480352CD207A395A6CB4B71
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Dear all,<br>
      <br>
      We know that the <a
        href=3D"https://tools.ietf.org/html/rfc7012#section-7">IANA
        considerations</a> mentions "expert review" for the <a
        href=3D"https://www.iana.org/assignments/ipfix/ipfix.xhtml">IPFIX
        registry</a>.<br>
      This BGP community is actually a special IPFIX Information Element
      as this is the first one based on <a
        href=3D"https://tools.ietf.org/html/rfc6313">RFC 6313=A0 </a>(bas=
icList,
      subTemplateList, subTemplateMultiList) <br>
      So it deserves special attention, review, and potential
      documentation as its own RFC.<br>
      <br>
      Regards, Benoit<br>
      =A0<br>
    </div>
    <blockquote
      cite=3D"mid:[email protected]"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3Dwindows-1252">
      <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"Microsoft YaHei UI";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Microsoft YaHei UI";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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;}
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 Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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]-->
      <div class=3D"WordSection1">
        <p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, dear all.<o:p></o=
:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">Nice meeting you in t=
he
            mail-list of IPFIX. This IETF in Berlin right now, we submit
            a draft and present it about the IPFIX IE extension when
            considering BGP community. I=92m looking for comments and
            feedbacks about our idea in new IE added in exporting the
            flow information correlated with BGP community. As dear
            chair told me that the mail-list is still alive, I follow
            the suggestion of putting my draft here and searching for
            advice and suggestions in the right place. <o:p></o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">Before that, I made a
            short summary of my draft which may be helpful in quick
            looking at the draft. When we consider traffic steering in
            our backbone network, we feel that the flow information
            based on BGP community is quite suitable. That=92s the reason
            why we write the draft. And we now recommend two IEs which
            may be assigned by IANA: bgpSourceCommunityList and
            bgpDestinationCommunityList. <o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">If you are facing up
            with this situations as us, then we can discuss about the
            IEs especially the details. <o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">The information of my
            draft: <a moz-do-not-send=3D"true"
href=3D"https://www.ietf.org/internet-drafts/draft-li-opsawg-ipfix-bgp-co=
mmunity-00.txt"
              target=3D"_blank"><span
                style=3D"font-size:10.0pt;font-family:&quot;Microsoft
                YaHei UI&quot;,sans-serif;background:white">https://www.i=
etf.org/internet-drafts/draft-li-opsawg-ipfix-bgp-community-00.txt</span>=
</a><o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">I=92m looking forward=
 for
            your comments.<o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards and have=
 a
            nice trip in Berlin.<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"text-align:left" align=3D"left"><=
span
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,sans-serif"
            lang=3D"EN-US">----------------------------------------------=
-------------<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"text-align:left" align=3D"left"><=
span
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,sans-serif"
            lang=3D"EN-US">Rong Gu<br>
            China Mobile Research Institute<br>
            No.32 Xuanwumen West Street, Xicheng District<br>
            Beijing, China, 100053<br>
            Mobile: +86 13811520541<br>
            Phone: +86 10 15801696688 Ext. 36211<br>
            Email: <a moz-do-not-send=3D"true"
              href=3D"mailto:[email protected]"><span
                style=3D"color:blue">[email protected]</span></a><o:=
p></o:p></span></p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
        <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>=A0</o:p></span>=
</p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------8480352CD207A395A6CB4B71--


--===============3737078665709395249==
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

--===============3737078665709395249==--