Skip to main content

A YANG Data Model for Routing Management
draft-ietf-netmod-routing-cfg-25

Yes

(Alia Atlas)
(Alvaro Retana)
(Benoît Claise)
(Deborah Brungard)

No Objection

(Alexey Melnikov)
(Alissa Cooper)
(Jari Arkko)
(Joel Jaeggli)
(Kathleen Moriarty)
(Mirja Kühlewind)
(Spencer Dawkins)
(Terry Manderson)

Note: This ballot was opened for revision 24 and is now closed.

Alia Atlas Former IESG member
Yes
Yes (for -24) Unknown

                            
Alvaro Retana Former IESG member
Yes
Yes (for -24) Unknown

                            
Benoît Claise Former IESG member
Yes
Yes (for -24) Unknown

                            
Deborah Brungard Former IESG member
Yes
Yes (for -24) Unknown

                            
Alexey Melnikov Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Alissa Cooper Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Ben Campbell Former IESG member
No Objection
No Objection (2016-11-01 for -24) Unknown
Should the reference to 6536. Be normative?
Jari Arkko Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Joel Jaeggli Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Kathleen Moriarty Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Mirja Kühlewind Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Spencer Dawkins Former IESG member
No Objection
No Objection (for -24) Unknown

                            
Stephen Farrell Former IESG member
No Objection
No Objection (2016-11-02 for -24) Unknown
If there exists a draft for a yang module that augments this
in a way that includes cryptographic values (e.g. maybe for an
IPsec VPN or something) then I think that'd be a nice addition
to section 11 as an informative reference.
Suresh Krishnan Former IESG member
No Objection
No Objection (2016-11-02 for -24) Unknown
* Have you considered including support for the Route Information Option (RFC4191)? Seems like it would be useful.

* default-lifetime is defined with a range of 0..9000 in this document but the upper limit will be raised to 65535 if and when draft-ietf-6man-maxra is approved. Is there a mechanism by which you can easily support this increased upper limit?
Terry Manderson Former IESG member
No Objection
No Objection (for -24) Unknown