Re: [IPFIX] [Ie-doctors] Search comments and feedbacks about the draft of IPFIX IE extension when considering BGP community
Paul Aitken <[email protected]> Fri, 29 Jul 2016 09:30:21 +0100
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
--===============5978503538005683026==
Content-Type: multipart/alternative;
boundary="------------FD53448449E9C88116C9082B"
--------------FD53448449E9C88116C9082B
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Li, two Information Element IDs are required for each basicList:
The first Information Element is the basicList itself. This element ID=20
goes in the IPFIX template "Information Element id" field as usual, per=20
figures G and L of RFC 7011. Effectively this is the outer "container"=20
element.
IDs 458 and 459 define basicList Information Elements, so these are the=20
first (outer, container) elements.
The second Information Element describes the type of each list element.=20
This goes in the basicList Field ID per Figure 1 of RFC 6313.=20
Effectively this is the inner "contained" element.
It's these second (inner, contained) elements which are missing.
Practically, we could have:
bgpSourceCommunityList (458) =3D list of bgpSourceAsNumber (16)
or
bgpSourceCommunityList (458) =3D list of sourceIPv4Address (8)
or in fact any other Information Element could be used as the "list of=20
..." element.
In order to ensure this Information Element is interoperable, the=20
missing element ID should be clearly stated in the draft.
P.
On 29/07/2016 09:10, [email protected] wrote:
> Hello P. Aitken and all,
>
> If the suggested IE numbers are assigned by IANA, 458 not 291 SHOULD=20
> be encoded in the Field ID field in the basicList for=20
> bgpSourceCommunityList, and 459 SHOULD be encoded for=20
> bgpDestinationCommunityList.
>
> basicList is an IE type defined in RFC6313. We can use this type to=20
> define new IEs if type basicList is applicable.
>
> Sorry for delayed response.
>
> Best Regards,
> -----------------------------------------------------------------------=
-
> [email protected]
>
> *From:* PJ Aitken <mailto:[email protected]>
> *Date:* 2016-07-20 22:49
> *To:* Benoit Claise <mailto:[email protected]>; Ariel Gu
> <mailto:[email protected]>; [email protected]
> <mailto:[email protected]>; [email protected]
> <mailto:[email protected]>; [email protected]
> <mailto:[email protected]>
> *CC:* lizhenqiang <mailto:[email protected]>; Brian
> Trammell <mailto:[email protected]>; [email protected]
> <mailto:[email protected]>
> *Subject:* Re: [IPFIX] Search comments and feedbacks about the
> draft of IPFIX IE extension when considering BGP community
> When a draft specifies one of the list types, should it also
> specify the type of the list elements and the expected semantics?
>
> Else we could have non-interoperable implementations exporting the
> same "IANA standard" information element, where one is a
> "basicList of X" while another is a "basicList of Y".
> ie, although the IE is the same, the basicList Field ID and
> semantics are different. See RFC 6313, Figure 1.)
>
> eg, the BGP community draft referenced below creates a new
> bgpSourceCommunityList. I suppose this may be a list of
> bgpSourceAsNumber, but that's not specified in the draft - so it
> could equally be a list of sourceIPv4Address or any other IE.
>
> Alternatively, devices could simply export IE #291 (basicList),
> with the bgpSourceCommunityList and bgpDestinationCommunityList
> disambiguated by the basicList Field ID contained in the basicList
> header. However that would be horrendous for collectors...
>
> P.
>
>
> On 20/07/16 08:12, Benoit Claise wrote:
>> Dear all,
>>
>> We know that the IANA considerations
>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf=
.org_html_rfc7012-23section-2D7&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3D=
Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNa=
ZBed3zfEKAlZ4zaux4&s=3DPT25lVmWADTBAoRFJls07fJ6PTOd2XWc0L4bTWxB3MY&e=3D>
>> mentions "expert review" for the IPFIX registry
>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.iana.o=
rg_assignments_ipfix_ipfix.xhtml&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3D=
Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNa=
ZBed3zfEKAlZ4zaux4&s=3Dtbt3wdaVgevcKVTqBEKX_MhNO7g_oaW3XiywAp65WgY&e=3D>.
>> This BGP community is actually a special IPFIX Information
>> Element as this is the first one based on RFC 6313
>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf=
.org_html_rfc6313&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729xYDYoCg=
BDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZBed3zfEKAlZ4=
zaux4&s=3DR9ipRubr7eEQrMnskDLzBjeZqhpnmefnWc59t3_ab7s&e=3D>(basicList,
>> subTemplateList, subTemplateMultiList)
>> So it deserves special attention, review, and potential
>> documentation as its own RFC.
>>
>> Regards, Benoit
>>
>>> Hi, dear all.
>>>
>>> Nice meeting you in the 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=E2=80=99m 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.
>>>
>>> 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=E2=80=99=
s the
>>> reason why we write the draft. And we now recommend two IEs
>>> which may be assigned by IANA: bgpSourceCommunityList and
>>> bgpDestinationCommunityList.
>>>
>>> If you are facing up with this situations as us, then we can
>>> discuss about the IEs especially the details.
>>>
>>> The information of my draft:
>>> https://www.ietf.org/internet-drafts/draft-li-opsawg-ipfix-bgp-co=
mmunity-00.txt
>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.=
org_internet-2Ddrafts_draft-2Dli-2Dopsawg-2Dipfix-2Dbgp-2Dcommunity-2D00.=
txt&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd=
1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZBed3zfEKAlZ4zaux4&s=3DT9dM=
bA_3xk8ZMfCI0dkNONKt1xL04aoMa8vn_-9FBns&e=3D>
>>>
>>> I=E2=80=99m 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]>
>>>
>>
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> [email protected]
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.or=
g_mailman_listinfo_ipfix&d=3DCwICAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729=
xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZBed3z=
fEKAlZ4zaux4&s=3DmL0br6tuMk78xRPYaHEPxZ5usdrXvvMI1C_g105zdws&e=3D =20
>
>
>
> _______________________________________________
> ie-doctors mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ie-doctors
--------------FD53448449E9C88116C9082B
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<div class=3D"moz-cite-prefix">Li, two Information Element IDs are
required for each basicList:<br>
<br>
<br>
The first Information Element is the basicList itself. This
element ID goes in the IPFIX template "Information Element id"
field as usual, per figures G and L of RFC 7011. Effectively this
is the outer "container" element.<br>
<br>
IDs 458 and 459 define basicList Information Elements, so these
are the first (outer, container) elements.<br>
<br>
<br>
The second Information Element describes the type of each list
element. This goes in the basicList Field ID per Figure 1 of RFC
6313. Effectively this is the inner "contained" element.<br>
<br>
It's these second (inner, contained) elements which are missing.<br=
>
<br>
<br>
Practically, we could have:<br>
<br>
=C2=A0=C2=A0=C2=A0 bgpSourceCommunityList (458) =3D list of bgpSour=
ceAsNumber (16)<br>
<br>
or<br>
<br>
=C2=A0=C2=A0=C2=A0 bgpSourceCommunityList (458) =3D list of sourceI=
Pv4Address (8)<br>
<br>
or in fact any other Information Element could be used as the
"list of ..." element.<br>
<br>
<br>
In order to ensure this Information Element is interoperable, the
missing element ID should be clearly stated in the draft.<br>
<br>
P.<br>
<br>
<br>
On 29/07/2016 09:10, <a class=3D"moz-txt-link-abbreviated" href=3D"=
mailto:[email protected]">[email protected]</a> wrote=
:<br>
</div>
<blockquote cite=3D"mid:[email protected]"
type=3D"cite">
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3DU=
TF-8">
<style>body { line-height: 1.5; }blockquote { margin-top: 0px; marg=
in-bottom: 0px; margin-left: 0.5em; }p { margin-top: 0px; margin-bottom: =
0px; }div.foxdiv20160729155728582415 { }body { font-size: 10.5pt; font-fa=
mily: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-hei=
ght: 1.5; }</style>
<div><span></span>Hello P. Aitken and all,</div>
<div><br>
</div>
<div>If the suggested IE numbers are assigned by IANA, 458 not 291
SHOULD be encoded in the Field ID field in the basicList for=C2=A0=
<span
style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt;
line-height: 1.5;">bgpSourceCommunityList, and 459=C2=A0</span>=
<span
style=3D"font-size: 10.5pt; line-height: 1.5; background-color:
window;">SHOULD be encoded for=C2=A0</span><span style=3D"font-=
size:
10.5pt; line-height: 1.5; background-color: window;">bgpDestina=
tionCommunityList.</span></div>
<div><span style=3D"font-size: 10.5pt; line-height: 1.5;
background-color: window;"><br>
</span></div>
<div><span style=3D"font-size: 10.5pt; line-height: 1.5;
background-color: window;">basicList is an IE type defined in
RFC6313. We can use this type to define new IEs if type
basicList is applicable.</span></div>
<div><br>
</div>
<div>Sorry for delayed response.</div>
<div><br>
</div>
<div>Best Regards,</div>
<hr style=3D"width: 210px; height: 1px;" align=3D"left"
color=3D"#b5c4df" size=3D"1">
<div><span>
<div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE:
10pt">
<div><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:liz=
[email protected]">[email protected]</a></div>
</div>
</span></div>
<blockquote style=3D"margin-top: 0px; margin-bottom: 0px;
margin-left: 0.5em;">
<div>=C2=A0</div>
<div style=3D"border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE:
12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef;
PADDING-BOTTOM: 8px; PADDING-TOP: 8px">
<div><b>From:</b>=C2=A0<a moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color: rgb(5=
,
99, 193); text-decoration: underline;">PJ Aitken</a></div=
>
<div><b>Date:</b>=C2=A02016-07-20=C2=A022:49</div>
<div><b>To:</b>=C2=A0<a moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color: rgb(5, =
99,
193); text-decoration: underline;">Benoit Claise</a>; <a
moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color:
rgb(5, 99, 193); text-decoration: underline;">Ariel Gu</a=
>;
<a moz-do-not-send=3D"true" href=3D"mailto:[email protected]"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;">[email protected]</a>; <a
moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color:
rgb(5, 99, 193); text-decoration: underline;">n.brownlee@=
auckland.ac.nz</a>;
<a moz-do-not-send=3D"true" href=3D"mailto:[email protected]=
u"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;">[email protected]</a></div>
<div><b>CC:</b>=C2=A0<a moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"colo=
r:
rgb(5, 99, 193); text-decoration: underline;">lizhenqiang=
</a>;
<a moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color:
rgb(5, 99, 193); text-decoration: underline;">Brian
Trammell</a>; <a moz-do-not-send=3D"true"
href=3D"mailto:[email protected]" style=3D"color: rgb(5=
,
99, 193); text-decoration: underline;">[email protected]=
g</a></div>
<div><b>Subject:</b>=C2=A0Re: [IPFIX] Search comments and
feedbacks about the draft of IPFIX IE extension when
considering BGP community</div>
</div>
</div>
<div>
<div class=3D"FoxDiv20160729155728582415"> When a draft
specifies one of the list types, should it also specify the
type of the list elements and the expected semantics?<br>
<br>
Else we could have non-interoperable implementations
exporting the same "IANA standard" information element,
where one is a "basicList of X" while another is a
"basicList of Y".<br>
ie, although the IE is the same, the basicList Field ID and
semantics are different. See RFC 6313, Figure 1.)<br>
<br>
eg, the BGP community draft referenced below creates a new
bgpSourceCommunityList. I suppose this may be a list of
bgpSourceAsNumber, but that's not specified in the draft -
so it could equally be a list of sourceIPv4Address or any
other IE.<br>
<br>
Alternatively, devices could simply export IE #291
(basicList), with the bgpSourceCommunityList and
bgpDestinationCommunityList disambiguated by the basicList
Field ID contained in the basicList header. However that
would be horrendous for collectors...<br>
<br>
P.<br>
<br>
<br>
<div class=3D"moz-cite-prefix">On 20/07/16 08:12, Benoit
Claise wrote:<br>
</div>
<blockquote
cite=3D"mid:[email protected]"
type=3D"cite" style=3D"margin-top: 0px;">
<div class=3D"moz-cite-prefix">Dear all,<br>
<br>
We know that the <a moz-do-not-send=3D"true"
href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf=
.org_html_rfc7012-23section-2D7&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2=
jTzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR=
_pCMk0ceVDm68IQNaZBed3zfEKAlZ4zaux4&s=3DPT25lVmWADTBAoRFJls07fJ6PTOd2=
XWc0L4bTWxB3MY&e=3D"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;">IANA considerations</a> mentions "expert
review" for the <a moz-do-not-send=3D"true"
href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.iana.o=
rg_assignments_ipfix_ipfix.xhtml&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi=
2jTzg&r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyA=
R_pCMk0ceVDm68IQNaZBed3zfEKAlZ4zaux4&s=3Dtbt3wdaVgevcKVTqBEKX_MhNO7g_=
oaW3XiywAp65WgY&e=3D"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;">IPFIX registry</a>.<br>
This BGP community is actually a special IPFIX
Information Element as this is the first one based on <a
moz-do-not-send=3D"true"
href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf=
.org_html_rfc6313&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DX=
x9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68I=
QNaZBed3zfEKAlZ4zaux4&s=3DR9ipRubr7eEQrMnskDLzBjeZqhpnmefnWc59t3_ab7s=
&e=3D"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;">RFC 6313=C2=A0 </a>(basicList,
subTemplateList, subTemplateMultiList) <br>
So it deserves special attention, review, and potential
documentation as its own RFC.<br>
<br>
Regards, Benoit<br>
=C2=A0<br>
</div>
<blockquote
cite=3D"mid:[email protected]=
om"
type=3D"cite" style=3D"margin-top: 0px;">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" ></o:shapedefaults>
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" ></o:idmap>
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1" style=3D"page: WordSection1;"=
>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US">Hi, dear
all.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US">Nice
meeting you in the 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=E2=80=99m 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></sp=
an></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><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=E2=80=99s the rea=
son 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" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><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" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US">The
information of my draft: <a
moz-do-not-send=3D"true"
href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.o=
rg_internet-2Ddrafts_draft-2Dli-2Dopsawg-2Dipfix-2Dbgp-2Dcommunity-2D00.t=
xt&d=3DCwMDEA&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729xYDYoCgBDd=
cp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZBed3zfEKAlZ=
4zaux4&s=3DT9dMbA_3xk8ZMfCI0dkNONKt1xL04aoMa8vn_-9FBns&e=3D"
target=3D"_blank" style=3D"color: rgb(5, 99, 193)=
;
text-decoration: underline;"><span
style=3D"font-size:10.0pt;font-family:"Mic=
rosoft
YaHei UI",sans-serif;background:white">htt=
ps://www.ietf.org/internet-drafts/draft-li-opsawg-ipfix-bgp-community-00.=
txt</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US">I=E2=80=99=
m looking
forward for your comments.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><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: justify;
margin: 0cm 0cm 0.0001pt; font-size: 10.5pt;
font-family: Calibri, sans-serif;" align=3D"left"><sp=
an
style=3D"font-size:10.0pt;font-family:"Verdana",sans-serif"
lang=3D"EN-US">------------------------------------=
-----------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align: justify;
margin: 0cm 0cm 0.0001pt; font-size: 10.5pt;
font-family: Calibri, sans-serif;" align=3D"left"><sp=
an
style=3D"font-size:10.0pt;font-family:"Verdana",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]"
style=3D"color: rgb(5, 99, 193); text-decoration:
underline;"><span style=3D"color:blue">gurong@chi=
namobile.com</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001p=
t;
text-align: justify; font-size: 10.5pt; font-family:
Calibri, sans-serif;"><span lang=3D"EN-US"><o:p>=C2=A0=
</o:p></span></p>
</div>
</blockquote>
<br>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">____________________________________________=
___
IPFIX mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:[email protected]" style=3D"color: rgb(5, 99, 193); text-decoration: un=
derline;">[email protected]</a>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" href=3D"https=
://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman_li=
stinfo_ipfix&d=3DCwICAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729=
xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZB=
ed3zfEKAlZ4zaux4&s=3DmL0br6tuMk78xRPYaHEPxZ5usdrXvvMI1C_g105zdws&=
e=3D" style=3D"color: rgb(5, 99, 193); text-decoration: underline;">https=
://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman_li=
stinfo_ipfix&d=3DCwICAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DXx9729=
xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=3DZslthyAR_pCMk0ceVDm68IQNaZB=
ed3zfEKAlZ4zaux4&s=3DmL0br6tuMk78xRPYaHEPxZ5usdrXvvMI1C_g105zdws&=
e=3D</a>=20
</pre>
</blockquote>
<br>
</div>
</div>
</blockquote>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">_______________________________________________
ie-doctors mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]"=
>[email protected]</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/ie-doctors">https://www.ietf.org/mailman/listinfo/ie-doctors</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------FD53448449E9C88116C9082B--
--===============5978503538005683026==
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
--===============5978503538005683026==--