escribes/g
>
>
> ___
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
Mahesh Jethanandani
mjethanand...@gmail.com
___
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs
pre-requisite however if the nh already exists and the
> nexthop-id is known, this should not be necessary. In addition, the text
> reads 'or return' which should rather be a result of querying the
> appropriate node in the data tree.
> - In 'IANA Considerations' - s/This document requests to register/This
> document registers/
>
> ___
> yang-doctors mailing list
> yang-doct...@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
Mahesh Jethanandani
mjethanand...@gmail.com
___
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs
Reviewer: Mahesh Jethanandani
Review result: Not Ready
I have reviewed this document as part of the Operational directorate’s ongoing
effort to review all IETF documents being processed by the IESG.
These comments were written with the intent of improving the
operational aspects of the IETF
The Last Call period for the above three drafts closed yesterday. Thanks to
everyone who provided comments on the three drafts.
The authors will update the documents based on the comments received and post
an updated version of the draft(s).
Mahesh & Mehmet.
> On Dec 15, 2015, at 2:09 PM, Ersu
decide whether the suggested presentation
would help clarify i2rs requirements to NETCONF. From a personal perspective it
would certainly help to have examples of how the requirements could be met.
Cheers.
Mahesh Jethanandani
mjethanand...@gmail.com
_
S Requirements
>
> Proceedings and slides can be found at:
> http://www.ietf.org/proceedings/interim/2015/06/24/i2rs/proceedings.html
> <http://www.ietf.org/proceedings/interim/2015/06/24/i2rs/proceedings.html>
>
> Sue Hares
>
>
>
mpus Ring 1 | 28759 Bremen | Germany
> > Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
> >
> > _______
> > i2rs mailing list
> > i2rs@ietf.org
> > https://www.ietf.org/mailman/listinfo/i2rs
> >
[Speaking as contributor]
Jeff,
I must have missed the previous reminder or notification about where to add
ephemeral requirements.
But would like to add the case which I described on the rtg-yang-coord mailing
list. Basically there is a requirement that certain configurations should not
be
