Re: [IPFIX] ipNextHopIPv6Address reported address

Nick Brown <brownn@Brocade.com> Mon, 08 June 2015 13:07 UTC

From: Nick Brown <brownn@Brocade.com>
To: "ietf@trammell.ch" <ietf@trammell.ch>
Thread-Topic: [IPFIX] ipNextHopIPv6Address reported address
Thread-Index: AQHQnragxqZ09DJjskmUvYozM+6f7J2cwR2AgAY9UIA=
Date: Mon, 08 Jun 2015 13:04:21 +0000
Message-ID: <1433768661.3691.14.camel@brocade.com>
References: <1433416039.22978.70.camel@brocade.com> <F8E56235-E3CD-433F-859E-616EA7124C19@trammell.ch>
In-Reply-To: <F8E56235-E3CD-433F-859E-616EA7124C19@trammell.ch>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-ID: <0D71259A7424A545B2CE86A0C606142A@brocade.local>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/IgmhojwlrpWXzURExy2dKmFypXI>
Cc: Derek Fawcus <dfawcus@Brocade.com>, Luca Boccassi <lboccass@Brocade.com>, Paul Atkins <patkins@Brocade.com>, "ipfix@ietf.org" <ipfix@ietf.org>, Doug Gordon <dgordon@Brocade.com>
Subject: Re: [IPFIX] ipNextHopIPv6Address reported address
Precedence: list
Reply-To: Nick Brown <brownn@Brocade.com>

On Thu, 2015-06-04 at 15:47 +0200, Brian Trammell wrote:
> > On 04 Jun 2015, at 13:07, Nick Brown <brownn@Brocade.com> wrote:
> > 
> > Hi All,
> > 
> > In a sentence, is it expected that ipNextHopIPv6Address should report
> > the global ipv6 address of the next hop when it has one, or may the link
> > local address be reported instead?
> > http://tools.ietf.org/html/rfc5102#section-5.7.3
> 
> First, the proper reference for the definitions of IEs in the IPFIX information model is http://www.iana.org/assignments/ipfix/ipfix.xhtml; per 7012, 5102 is no longer considered authoritative for IE definitions.
> 
> (In this case, though, this is an admittedly pedantic distinction; the content is identical).
> 
> > There are obvious cases where the next hop may only have link local
> > address, if example it's only configured that way. But in other cases
> > where it may have both a link local and global address it's often the
> > case that routing protocols may use local addresses to setup the
> > forwarding plane where traffic is being observed. Thus at the point in
> > the forwarding path that traffic is being observed this all that is
> > available, and it's not apparent that a mapping from link local address
> > to global address (where is exists) can be done.
> 
> The way I read this, if the address is not being changed as part of the packet handing (on which see the fifth point in section 2.3 of RFC 7012), the address to report is the address the packets are sent to in the context of the egress interface. If the connection between the device the MP is on and the next hop has link-local addresses only, then the link-local address is the correct one to export.

ipNextHopIPv6Address is a derived field, derived from the treatment of
the packet by the switching path that constitutes our Observation point.
While at the global network level and possibly at the configuration
level of the IPFIX Device's Metering Process the interface of the Next
Hop may have both a link local IPV6 address and global IPV6 address, the
only one readily available to the Metering Process is the link local
address used by the switching path to do it's work, so that is what we
report.

Cheers,
Nick

[IPFIX] ipNextHopIPv6Address reported address Nick Brown
Re: [IPFIX] ipNextHopIPv6Address reported address Brian Trammell
Re: [IPFIX] ipNextHopIPv6Address reported address Nick Brown