Re: [IPFIX] RFC 6728: Observation Point ID definition
Gerhard Muenz <[email protected]> Sat, 11 Mar 2017 14:13:47 +0100
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============2743681440897326616==
Content-Type: multipart/alternative;
boundary="------------5BA4A5D252CA0A1BAC9EA559"
This is a multi-part message in MIME format.
--------------5BA4A5D252CA0A1BAC9EA559
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Hello Marta,
Observation Point is an IPFIX term defined in RFC5101 and then RFC7011 (
https://tools.ietf.org/html/rfc7011#page-8 ):
Observation Point
An Observation Point is a location in the network where packets
can be observed. Examples include a line to which a probe is
attached; a shared medium, such as an Ethernet-based LAN; a single
port of a router; or a set of interfaces (physical or logical) of
a router.
The ObservationPoint class defined in RFC6728 (
https://tools.ietf.org/html/rfc6728#section-4.1 ) allows to identify
such an Observation Point in a Monitoring Device.
It seems that you do not want to specify a point for observing packets,
right? Then, the ObservationPoint class is not the right class for your
use case.
You can define your own yang module or extend the existing one with a
new class that allows to identify your source of statistics, whatever
that shall be.
Regards,
Gerhard
On 04.03.2017 17:21, Marta Seda wrote:
>
> Hello,
>
> RFC 6728 defines the observation point as the location for which
> packets are 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 = "both" | | SelectionProcess |
>
> +-------------------------------+ +------------------+
>
> In RFC 6728, the observationpointid, ifname, ifindex,entphysicalname
> and entphysicalindex are part of the observationpointparameters grouping.
>
> RFC 6728 has examples centered around the idea of creating a metering
> process that samples packets and reports statistics over ipfix
> (netflow-like statistics).
>
> There is yang models that configure statistic collection. 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 attempt to do that via the use
> of IfName, IfIndex, EntPhysicalName and EntPhysicalIndex (which are
> SNMP physical entities). However you have logical entities that the
> current structure doesnt permit you to define as the observation
> points. Is that a correct interpretation of the current yang for
> ipfix? How can you refer to logical entities? (it seems the only
> 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
>
>
>
> _______________________________________________
> IPFIX mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix
--------------5BA4A5D252CA0A1BAC9EA559
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">
<br>
Hello Marta,<br>
<br>
Observation Point is an IPFIX term defined in RFC5101 and then
RFC7011 ( <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc7011#page-8">https://tools.ietf.org/html/rfc7011#page-8</a> ):<br>
<br>
<pre class="newpage"> Observation Point
An Observation Point is a location in the network where packets
can be observed. Examples include a line to which a probe is
attached; a shared medium, such as an Ethernet-based LAN; a single
port of a router; or a set of interfaces (physical or logical) of
a router.</pre>
<br>
The ObservationPoint class defined in RFC6728 (
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc6728#section-4.1">https://tools.ietf.org/html/rfc6728#section-4.1</a> ) allows to identify
such an Observation Point in a Monitoring Device.<br>
<br>
It seems that you do not want to specify a point for observing
packets, right? Then, the ObservationPoint class is not the right
class for your use case.<br>
<br>
You can define your own yang module or extend the existing one with
a new class that allows to identify your source of statistics,
whatever that shall be.<br>
<br>
Regards,<br>
Gerhard<br>
<br>
<br>
<div class="moz-cite-prefix">On 04.03.2017 17:21, Marta Seda wrote:<br>
</div>
<blockquote
cite="mid:BY2PR0501MB17346D370676D56617BC67A49C2A0@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:"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="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">RFC 6728 defines the observation point as
the location for which packets are observed. RFC 6727 page
4.1 shows this uml relationship:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black">
+-------------------------------+<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
ObservationPoint |<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black">
+-------------------------------+<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
name |<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> | observationPointId
{readOnly} |<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
observationDomainId | 0..*<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
ifName[0..*] |-------------+<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
ifIndex[0..*] | | 0..*<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
entPhysicalName[0..*] | V<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> |
entPhysicalIndex[0..*] | +------------------+<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black"> | direction =
"both" | | SelectionProcess |<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black">
+-------------------------------+ +------------------+<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In RFC 6728, the observationpointid,
ifname, ifindex,entphysicalname and entphysicalindex are part
of the observationpointparameters grouping.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">RFC 6728 has examples centered around the
idea of creating a metering process that samples packets and
reports statistics over ipfix (netflow-like statistics).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is yang models that configure
statistic collection. 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 attempt to do that via
the use of IfName, IfIndex, EntPhysicalName and
EntPhysicalIndex (which are SNMP physical entities). However
you have logical entities that the current structure doesnt
permit you to define as the observation points. Is that a
correct interpretation of the current yang for ipfix? How can
you refer to logical entities? (it seems the only place you
could do this was to stick the leaf-ref into the name but not
a good yang practice).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please advise.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marta Seda<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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://www.ietf.org/mailman/listinfo/ipfix">https://www.ietf.org/mailman/listinfo/ipfix</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------5BA4A5D252CA0A1BAC9EA559--
--===============2743681440897326616==
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
--===============2743681440897326616==--