Hi Acee,
Thanks for your comments!
This data model is totally aligned with the definition of the info model that
has already passed the WG LC. So, I think the first step is to discuss whether
the changes should be made to the info model. If there is a consensus to make
the changes, it should be easy to update the data model accordingly.
In the model, the description of the tunnel-encap nexthop says:
"This can be an encap representing an IP tunnel or
MPLS tunnel or others as defined in info model.
An optional egress interface can be chained to the
tunnel encap to indicate which interface to send
the packet out. The egress interface is useful
when the network device contains Ethernet interfaces
and one needs to perform address resolution for the
IP packet.";
So, IMHO, the model just treats a tunnel as the nexthop, it does not intend to
create a tunnel and just uses an existing one.
Best regards,
Mach
> -----Original Message-----
> From: Acee Lindem (acee) [mailto:[email protected]]
> Sent: Tuesday, November 24, 2015 3:56 AM
> To: Mach Chen; [email protected]
> Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-04.txt
>
> Hi Mach,
>
> I’m looking at draft-ietf-i2rs-rib-data-model-04.txt and it still includes
> all the
> tunnel encaps. I know you received several comments that those should be in
> the tunnel model(s) and this I2RS RIB model should merely reference an
> imported tunnel abstraction. How are you going to address this? It seemed
> that the consensus (and an opinion that I share) was that this model should
> not
> attempt to generically created tunnels via RIB/FIB entries.
> Thanks,
> Acee
>
> On 11/23/15, 2:23 AM, "i2rs on behalf of Mach Chen" <[email protected]
> on behalf of [email protected]> wrote:
>
> >Hi,
> >
> >We just uploaded an update that addresses the comments received
> >(include online and offline) recently. Please review the draft and comment!
> >
> >Thanks,
> >Mach
> >
> >> -----Original Message-----
> >> From: i2rs [mailto:[email protected]] On Behalf Of
> >>[email protected]
> >> Sent: Monday, November 23, 2015 3:16 PM
> >> To: [email protected]
> >> Cc: [email protected]
> >> Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-04.txt
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >>directories.
> >> This draft is a work item of the Interface to the Routing System
> >>Working Group of the IETF.
> >>
> >> Title : A YANG Data Model for Routing Information
> Base
> >> (RIB)
> >> Authors : Lixing Wang
> >> Hariharan Ananthakrishnan
> >> Mach(Guoyi) Chen
> >> Amit Dass
> >> Sriganesh Kini
> >> Nitin Bahadur
> >> Filename : draft-ietf-i2rs-rib-data-model-04.txt
> >> Pages : 65
> >> Date : 2015-11-22
> >>
> >> Abstract:
> >> This document defines a YANG data model for Routing Information Base
> >> (RIB) that aligns with the I2RS RIB information model.
> >>
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/
> >>
> >> There's also a htmlized version available at:
> >> https://tools.ietf.org/html/draft-ietf-i2rs-rib-data-model-04
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-data-model-04
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> >>submission until the htmlized version and diff are available at
> >>tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> i2rs mailing list
> >> [email protected]
> >> https://www.ietf.org/mailman/listinfo/i2rs
> >
> >_______________________________________________
> >i2rs mailing list
> >[email protected]
> >https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
