Skip to main content

A YANG Data Model for Routing Management
RFC 8022

Yes

Alvaro Retana
(Alia Atlas)
(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.

Alvaro Retana Yes

(Alia Atlas; former steering group member) Yes

Yes (for -24)

                            

(Benoît Claise; former steering group member) Yes

Yes (for -24)

                            

(Deborah Brungard; former steering group member) Yes

Yes (for -24)

                            

(Alexey Melnikov; former steering group member) No Objection

No Objection (for -24)

                            

(Alissa Cooper; former steering group member) No Objection

No Objection (for -24)

                            

(Ben Campbell; former steering group member) No Objection

No Objection (2016-11-01 for -24)
Should the reference to 6536. Be normative?

(Jari Arkko; former steering group member) No Objection

No Objection (for -24)

                            

(Joel Jaeggli; former steering group member) No Objection

No Objection (for -24)

                            

(Kathleen Moriarty; former steering group member) No Objection

No Objection (for -24)

                            

(Mirja Kühlewind; former steering group member) No Objection

No Objection (for -24)

                            

(Spencer Dawkins; former steering group member) No Objection

No Objection (for -24)

                            

(Stephen Farrell; former steering group member) No Objection

No Objection (2016-11-02 for -24)
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 steering group member) No Objection

No Objection (2016-11-02 for -24)
* 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 steering group member) No Objection

No Objection (for -24)