[IPFIX] RFC 6728: Observation Point ID definition
Marta Seda <[email protected]> Sat, 4 Mar 2017 16:21:51 +0000
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <BY2PR0501MB17346D370676D56617BC67A49C2A0@BY2PR0501MB1734.namprd05.prod.outlook.com> |
--===============5646389411929294596==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_BY2PR0501MB17346D370676D56617BC67A49C2A0BY2PR0501MB1734_"
--_000_BY2PR0501MB17346D370676D56617BC67A49C2A0BY2PR0501MB1734_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello,
RFC 6728 defines the observation point as the "location for which packets a=
re observed". RFC 6727 page 4.1 shows this uml relationship:
+-------------------------------+
| ObservationPoint |
+-------------------------------+
| name |
| observationPointId {readOnly} |
| observationDomainId | 0..*
| ifName[0..*] |-------------+
| ifIndex[0..*] | | 0..*
| entPhysicalName[0..*] | V
| entPhysicalIndex[0..*] | +------------------+
| direction =3D "both" | | SelectionProcess |
+-------------------------------+ +------------------+
In RFC 6728, the observationpointid, ifname, ifindex,entphysicalname and en=
tphysicalindex are part of the observationpointparameters grouping.
RFC 6728 has examples centered around the idea of creating a metering proce=
ss that samples packets and reports statistics over ipfix (netflow-like sta=
tistics).
There is yang models that configure statistic collection. It seems in tha=
t case (if you want to use ipfix to carry those statistics), that the obser=
vation point could refer to those entities (leaf-ref) that are already coll=
ecting statistics. When I look at the RFC 6728 yang structure it seems the=
re is an "attempt" to do that via the use of IfName, IfIndex, EntPhysicalNa=
me and EntPhysicalIndex (which are SNMP physical entities). However you ha=
ve logical entities that the current structure doesn't permit you to define=
as the observation points. Is that a correct interpretation of the curren=
t yang for ipfix? How can you refer to logical entities? (it seems the onl=
y place you could do this was to stick the leaf-ref into the name but not a=
good yang practice).
Please advise.
Thanks.
Marta Seda
--_000_BY2PR0501MB17346D370676D56617BC67A49C2A0BY2PR0501MB1734_
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:"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;}
/* 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
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:"Courier New";}
span.grey
{mso-style-name:grey;}
.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;}
--></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 lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">RFC 6728 defines the observation point as the “=
;location for which packets are observed”. RFC 6727 page 4.1 sh=
ows this uml relationship:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; +-------------------------------+<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | ObservationPoint =
|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nb=
sp;+-------------------------------+<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | name =
&nb=
sp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | observationPointId {readOnly} |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | observationDomainId &nb=
sp; | 0..*<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | ifName[0..*] &nbs=
p; |-------------+<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | ifIndex[0..*] &nb=
sp; | &nbs=
p; | 0..*<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | entPhysicalName[0..*] =
| V=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | entPhysicalIndex[0..*] |&nbs=
p; +------------------+<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; | direction =3D "both" &nbs=
p; | | SelectionProcess |<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Co=
urier New";color:black"> &nbs=
p; +-------------------------------+ +-------=
-----------+<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">In RFC 6728, the observationpointid, ifname, ifindex=
,entphysicalname and entphysicalindex are part of the observationpointparam=
eters grouping.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">RFC 6728 has examples centered around the idea of cr=
eating a metering process that samples packets and reports statistics over =
ipfix (netflow-like statistics).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">There is yang models that configure statistic collec=
tion. It seems in that case (if you want to use ipfix to carry =
those statistics), that the observation point could refer to those entities=
(leaf-ref) that are already collecting statistics.
When I look at the RFC 6728 yang structure it seems there is an R=
20;attempt” to do that via the use of IfName, IfIndex, EntPhysicalNam=
e and EntPhysicalIndex (which are SNMP physical entities). However yo=
u have logical entities that the current structure doesn’t
permit you to define as the observation points. Is that a correct in=
terpretation of the current yang for ipfix? How can you refer to logi=
cal entities? (it seems the only place you could do this was to stick the l=
eaf-ref into the name but not a good yang
practice).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Please advise.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Thanks.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Marta Seda<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>
--_000_BY2PR0501MB17346D370676D56617BC67A49C2A0BY2PR0501MB1734_--
--===============5646389411929294596==
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
--===============5646389411929294596==--