1. Routing Area Open Meeting Maastricht, July 2010 Area Directors Adrian Farrel Stewart Bryant

2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: –The IETF plenary session –The IESG, or any member thereof on behalf of the IESG –Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices –Any IETF working group or portion thereof –The IAB or any member thereof on behalf of the IAB –The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).RFC 5378RFC 3979RFC 4879 Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.RFC 5378RFC 3979 A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

3. Note Also… Please state your name clearly before speaking at the microphone Audio streams at http://tools.ietf.org/agenda/78/ Jabber –Please try to have someone monitor jabber in your meetings –http://www.ietf.org/meeting/78/jabber.html –This meeting at rtgarea@jabber.ietf.org You do know about the Routing Area mailing list? –routing-discussion@ietf.org Blue Sheets Minutes

4. Today’s Agenda Routing Area Directorate Update (Deborah) Working Group Reports ADnits: Things ADs usually complain about Manageability Considerations –Experience from PCE (Julien) –Recommendations from the Ops Area : RFC 5706 (TBD) –OAM Workshop proposal and plans (Adrian) Using the Ticketing System in Your WG (JP) Thinking about Congestion (David Black) Any Other business

5. Routing Directorate Update http://www.ietf.org/iesg/directorate/routing.html Coordinators appointed –Deborah Brungard –Dan Li (back-up) Current status and experience (Deborah)

6. Working Group Reports BFD CCAMP FORCES IDR IS-IS KARP L2VPN L3VPN MANET MPLS –MPLS-TP *OSPF PCE PIM *PWE3 ROLL RTGWG SIDR *VRRP

7. OSPF WG Update Not meeting in Maastricht, Will meet in Beijing RFC 5838 – Support of Address Families in OSPFv3 published. OSPF Multi-Instance/Transport Instance Drafts – will query CCAMP to see if optical vendors have intent to implement New Drafts (non-WG) –Update on OSPFv3 Router Bit – Refresh pending –Update on stub area for OSPFv3 – Not presented yet CCAMP Drafts with OSPF Implications –RFC5787bis – ASON Routing Update –OSPF TE Encoding for WDM network signaling (multiple drafts)

8. PWE3 Issues From The List Three issues to be discussed Tuesday AM: 1.CW currently mandatory for MPLS-TP PWs - should this be relaxed? Been requested on the list 2.Use of GAL on PWs If CW restriction is relaxed, then need GAL for GACH- based OAM Would need to update RFC5586 to allow GAL on PWs 3.Preferred CC-type for VCCV Currently 3 VCCV control channel types: CW/GACH, Router Alert and TTL Looking for a preferred mode for future implementations Will conduct implementation & deployment survey Related to two previous issues

9. VRRP WG Status Chairs Mukesh Gupta, Juniper Networks Radia Perlman, Intel VRRP version 3 for IPv4 and IPv6 (unified) RFC 5798 was published VRRP unified MIB WGLC Completed. Comments incorporated. Ready for AD Review WG ready to be concluded

10. ADnits Suggested by Dave Ward A collection of issues often raised in AD review or IESG review Based on observations of other ADs and these ADs’ current behaviour patterns –Not “rules that must be obeyed” –Warnings of things that sometimes come as “late surprises” –Intended as an aid to help you get your I-D approved more quickly Captured on the Routing Area Wiki –http://trac.tools.ietf.org/area/rtg/trac/wiki

11. ADnits Overview Do not propose to discuss them here –Happy to have off-line discussions –Recall: the purpose is to help not hinder Highlights –Why Experimental? –How obsoleting other RFCs –Follow RFC Editor preferences and style –Consider manageability and congestion –Internationalisation concerns –Formal language –Dates and times –Protocol versioning

12. Manageability Considerations PCE has been trialling this –draft-ietf-pce-manageability-requirements –Now going to Historic RFC Ops Area made more general –RFC 5706 –NOT requirements –Strong advice and guidance Good protocols are manageable Experience from PCE (Julien) Advice for the future – RFC 5706 (TBD)

13. OAM Workshop Late stage planning –Probably October 12-14 –Probably George Mason University, Virginia, USA –Announcement/invitation soon –More details http://www3.tools.ietf.org/area/ops/trac/wiki/oamWorkshop soon –More details from the OPS ADs Purpose –Discover and document operational requirements and constraints for tunnelled forwarding plane OAM –The scope of this workshop is limited to the forwarding plane Control plane and management plane out of scope Prerequisites –Those intending to make presentations must submit position papers to the IAB/IESG by August 27 One to five pages on a solution of emphasis to the IETF Paper evaluation/selection by a technical programme committee Programme published c. September 10 –Limited space for those not presenting a paper –Papers will be published in a public forum

14. Thinking About Congestion What does this mean? Why is it important? David Black

15. Using the Ticketing System A.k.a. Issue Tracking JP Vasseur

16. Any Other Business