IETF-82 Routing Area Open Meeting
=================================

http://rtg.ietf.org 
ADs: Stewart Bryant, Adrian Farrel

Scribes: Deborah Brungard 

Administriva and Area Status
----------------------------
Stewart: Reviewed the Note Well. Reminded to try and use Jabber. Reminded about Routing Area
mailing list and wiki. 



Routing Area Working Group Reports
----------------------------------

BFD (Adrian) - Not meeting this time, progressing P2MP.

CCAMP (Lou) – We are meeting twice. Covering G709 and WSON, next session Flexible Grid. We had 3 rfcs,
one in queue,2 with IESG.

Forces (Joel-proxy chair) - Meeting went well on Monday. LFB Library document review: plan to make WG LC
after some reviews. CE HA document review: MAY require an update before WG LC. Complete 3 outstanding drafts:
Interop -bis document is simpler update. Plan: Shutdown after the above work.

IDR (John) - New Working Group Documents (as of today): draft-wkumari-idr-as0-01,
draft-keyupate-idr-bgp-gr-notification-00,draft-keyur-idr-enhanced-gr-00. Multiple new WG adoption requests
(on list shortly). Sent (back) to RFC Ed – deprecate-as-sets. IDR work areas: (1) Error handling – significant
progress, WG consensus. More to do (q.v. GROW requirements doc, other error,robustness and debug related drafts).
(2) The never-ending battle against rust: updates to route reflection,graceful restart – underway.
(3) Upcoming work – multiple paths, route selection and convergence related. (4) And a partridge in a pear tree.
Chairs working to clear backlog.

ISIS (Adrian) - Not meeting this time. They are working, but no meeting.

KARP (Brian) - KARP meets Wednesday afternoon. We'll start with a WG discussion on a DISCUSS that Russ Housley
has on our document describing what KARP design teams are to do. We will have a discussion on IS-IS security gaps
and would appreciate those with IS-IS knowledge to attend the discussion. We will have several presentations on
key management for routing protocls.

L2VPN (Gilles) - Two sessions this week. First on traditional items, 2nd on DCN, need to decide sort out between
L2VPN and L3VPN.
 
L3VPN (Ben) - We have 5 drafts in RFC Editor queue that were blocking on normative references (some of them
for close to 2 years). The references have now been submitted so those drafts are unblocked and just waiting
on the RFC Editor to do the editing/publication as RFCs. Our session this week is focussed on VPN for Data Centers
(VPN4DC) and if that's a topic of interest to folks, whether they think IETF should or should not do work in
that area they should come to L3VPN tomorrow afternoon.

MANET (Dan) - Couple of documents moving forward. Adrian be advised I will be asking on a document you've had
for a long time and now plan to move forward.

MPLS (Ross) - 10 new RFCs, 6 ready for assignment, more in editors queue. One session Monday, one on Thursday
afternoon. MPLS-TP most published or ready. We completed all milestones in charter, so need to update. If chairs
forgot something, just bug us.

OSPF (Adrian) -  Not meeting, plan for Paris to meet. Drafts close to becoming RFCs: (1) Supporting Authentication
Trailer for OSPFv3 (IESG Review), (2) OSPF Multi-Instance Extensions (Publication Requested). New WG Documents:
(1) OSPF Hybrid Broadcast and P2MP Interface Type (2) Use of OSPF-MDR in Single-Hop Broadcast Networks, (3) OSPF
Traffic Engineering (TE) Metric Extensions. Active WG Documents: (1) Routing for IPv4-embedded IPv6 Packets,
(2) Hiding Transit-only Networks in OSPF, (3) OSPF Stub Router Advertisement, (4) Security Extension for OSPFv2
when using Manual Key Management, (5) OSPF Transport Instance Extensions. New Drafts to discuss in Paris:
(1) OSPFv3 Auto-Configuration, (2) OSPF Topology-Transparent Zone, (3) Prefix Assignment in a Home Network (if
approach accepted by HOMENET WG).

PCE (Julian) – No new RFCs. Meet Thursday afternoon. Stateful PCE discussing - 2 drafts.

PIM (Mike) - Met this morning. 6420 published. New effort to update and effort on a questionaire to implementers
and operators on what being used. PIM port need to finish up.

PWE3 (Andy) - PWE3 will be meeting on Wednesday morning. Since the last IETF, we have three new RFCs. We also
have one draft in the RFC Editor's queue that is awaiting an external reference. We currently have four drafts
with the IESG, one of which, static PW status, is in the process of being updating to include IESG comments. The
new revision is expected while we're here in Taipei. This is the last major draft needed for the first set of
MPLS-TP RFCs. We have a couple of drafts awaiting updates to reflect WG last call comments, and they will then be
submitted to the IESG. We have a healthy number of other ongoing drafts, and people keep bringing in new proposals.
The VCCV-2 draft is probably the biggest generator of WG discussion right now, and we're asking for continuing
discussion on the list. Other than that,all is well.

ROLL (Adrian) - Pushing on with its work doing capability statements for ripple draft. Finaly should see complete
as RFC by Christmas. Working on experimental extension.

RTGWG (Alvaro) - Discussing update to charter to deal with SSR. Talked about composite link and trees.

SIDR (Sandy) - SIDR met on Tuesday at 1300. WG status is that we have 14 documents in the RFC Editor queue, one
for which publication is requested, four in various stages of last call and 10 that are active.  We discussed
recent changes to a small number of drafts and some of the issues that arose during recent last calls.  The 
discussions that started on the list (route leaks, algorithm agility) were energetic and productive.Discussions
were so energetic that the wg ran long, which unfortunately shortened the presentations about an open-source
implementation, mibs, and estimates of CPU load.

Adrian - We have a BoF this time chaired by Lou and Wes: SDN BoF.
Wes: Read description - BoF not to form wg, but to understand use cases and what SDN is not.

Routing Directorate (Adrian)
----------------------------
Adrian reviewed the slide. Noted, reviews for both within RA and outside RA. You can also request for an early
review of one of your documents. ADs will be using this more going forward (as the graphs indicate). Reviewers
on a rotating term, give option for people to be released and new people to join.
Dimitri - Do the numbers represent what you review or what the Directorate reviews?
Adrian - What the Directorate reviews.
Stewart - We do 10-20 every fortnight.
Adrian - Not quite every fornight. Depends if holidays, etc.
stewart - We don't run it like Security, where every one gets reviewed, just ones we think need extra attention.

Stochastic Routing (Dimitri)
----------------------------

Presented slides, asked to consider how to do this, if people have views?
Adrian - This is relevant to questions just starting to surface on what type of metrics might be useful for MPLS TE
e.g. delay. which will stretch the protocol.
Dimitri - With IGPs, it's flooded to everyone, not targeted, so those will get, that don't need. Raises questions on
parameters that are not route related. Also need to consider if have a reverse route which don't always have.
Sue - There's distributed file information, not policy, policy is another dimension. If represent as a flat space may
be missing the dynamic that is useful. Suggesting this type of thing can be used to classify as policy vs. non-policy.
Need a taxonomy that is a bit more algorithmic, e.g. what can be done offline. 
Adrian - Are you doing this work, somewhere?
Dimitri - Doing as experiments now, but one day will be running in the field.
Adrian - If people want to discuss this with you - is there a Forum or your email address?
Dimitri- My email or this routing discussion mailing list.
Adrian - That would be a good use of the list.

Adrian - Other topic - AOB. Routing at other layers. Discussion in Paris? e.g. Operations Area.
We should make decision, should we be more productive or don't care. I'm proposing in the Area meeting in Paris we
will look at what is going on in other areas.
Dimitri - Based on this and previous discussion. Where are the root concepts of routing documented? Maybe by looking
at introduction of different documents, one can summarize. But what can we offer?
Adrian - I can see that those in this room don't want to write those documents. Probably should talk to IAB, they have
those type of documents.
Any other business?
Adrian - Those interested in BGP - something is going on in savi in the next slot. 


Open Discussion
---------------
No discussion.