Skip to main content

Traffic Engineering Architecture and Signaling
charter-ietf-teas-02

Yes

(Adrian Farrel)
(Alia Atlas)
(Jari Arkko)

No Objection

(Alissa Cooper)
(Brian Haberman)
(Joel Jaeggli)
(Kathleen Moriarty)
(Richard Barnes)
(Stephen Farrell)
(Ted Lemon)

Note: This ballot was opened for revision 00-01 and is now closed.

Ballot question: "Is this charter ready for external review?"

Adrian Farrel Former IESG member
Yes
Yes (for -00-01) Unknown

                            
Alia Atlas Former IESG member
Yes
Yes (for -00-02) Unknown

                            
Jari Arkko Former IESG member
Yes
Yes (for -00-03) Unknown

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

                            
Barry Leiba Former IESG member
No Objection
No Objection (2014-11-23 for -00-02) Unknown
(Editorial comments fixed in -02; thanks.)
Benoît Claise Former IESG member
No Objection
No Objection (2014-11-25 for -00-03) Unknown
"The TEAS WG will work on the following topics:"
It seems like a list of deliverables.
I understand it's not, as the deliverables are part of the list "The TEAS working group is chartered to deliver the following:", which is a subset (or phase 1) of the first list AFAICT.

Proposal:
OLD:
"The TEAS WG will work on the following topics:"

NEW:
"The TEAS WG is responsible for:"


There is a discrepancy between

 f) Definition and extension of management and security techniques 
    for RSVP-TE signaling. This includes YANG and MIB modules for
    configuring and monitoring RSVP-TE as well as mechanisms used
    to configure, control, and report OAM within TE networks. 


and 

 6. YANG models for a Traffic Engineering Database in coordination
    with working groups working on YANG models for network
    topology and for technology-specific network attributes.

Do you really want YANG and MIB?

NEW:

 Definition and extension of management and security techniques 
 for RSVP-TE signaling, includes configuring and monitoring RSVP-TE 
 as well as mechanisms used to configure, control, and report OAM 
 within TE networks. YANG and MIB modules may be considered.
Brian Haberman Former IESG member
No Objection
No Objection (for -00-02) Unknown

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

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

                            
Martin Stiemerling Former IESG member
No Objection
No Objection (2014-11-25 for -00-02) Unknown
Fine charter, I wonder just if this should mention any coordination with the RSVP directorate when talking about RSVP-TE, since the charter mentions a number of contact points with other WGs
Pete Resnick Former IESG member
No Objection
No Objection (2014-11-24 for -00-02) Unknown
"Requirements" appear in work items 2 and 5. Since we've had recent discussions about whether we want to require publication of "requirements", I was wondering if we might consider re-wording those a bit to not appear to require said publication. No objection to external review, though.
Richard Barnes Former IESG member
No Objection
No Objection (for -00-02) Unknown

                            
Spencer Dawkins Former IESG member
No Objection
No Objection (2014-11-24 for -00-02) Unknown
I agree with Pete's comment re: requirements documents.
Stephen Farrell Former IESG member
No Objection
No Objection (for -00-02) Unknown

                            
Ted Lemon Former IESG member
No Objection
No Objection (for -00-02) Unknown