IETF-81 Routing Area Open Meeting
=================================

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

Scribes: Deborah Brungard 

Administriva and Area Status
----------------------------
Adrian: Reviewed the Note Well. Reminded to try and use Jabber. Reminded about Routing Area
mailing list and wiki. Adrian announced that he is now funded by Juniper Networks.

The routing directorate is working very well,thanks everyone. The review process we
have now is the ADs review pretty through to help get thru the IESG. Happy to hear comments
or complaints about that process. ITU has two liaisons, the two of us, Stuart and Adrian.
That's not too good for us with our work load so we are asking to have new liaisons assigned.

Please make sure to get IPRs into the process as early as possible.

No BoFs this time.

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

BFD (Adrian) - didn't meet. Charter update on the next IESG agenda. Pretty minor, refocusing,
picking up p2mp, and protocol maintenance mode. I will hand over to stewart for responsibility.

CCAMP (Lou) – Met twice, active topics are OTN and WSON and some on MPLSTP. Two recent WSON
related RFCs,two in editors queue, 1 draft with IESG, 3 post WG LC, soon to be passed to IESG.
Exchanged liaisons with ITU SG15 on ASON routing support, getting close to completing. Good progress
on closing a major issue with OTN, long discussion on WSON, no clear consensus in meeting,
basically split.

Forces (Jamal) - We had a meeting on Monday which was well attended. The discussion on the LFB
library took the most of our time. That document is  in good shape now and we hope to make small
updates which are editorial in nature. The other two outstanding work group document are also in
the same state. We hope to push all 3 documents for publication. We dont plan to take any new work
for the current charter (and plan to shutdown the WG). We are seeing more uptake on implementation
(although nothing being public).

IDR (John) - We had a meeting did alot of items, a new rfc, four more soon to headed to IESG. Pile
of new documents (six). My take is that the large areas are - error handling, manageability,
robustnes/scaling.

ISIS (Acee reported for them) - Presentation on interops for shortest path bridging. Over the top
tlv presentation which also is being looked at in the Routing Area wg. Presentation on oam using a
separate instance for trill.

KARP (Joel) - One document, the design guidelines document, has completed IETF last call.
One document, the threats document, is in IETF Last call.
Good progress is being made on several protocol analysis documents.
The key tables document should be ready for WG last call very shortly.
Work is beginning on the key management work items.  There are several 
proposals on the table.
Adrian - All of you need in your protocol documents to be aware of karp work, so please review
their documents.

L2VPN (Gilles) - One done, 3 more. Many ready for last call. Will be rechartering, a few new items
suggested this IETF for it. So we need to nail down. After recharter will probably have quite a 
few documents which are now individual.
 
L3VPN (Ben) - Since last IETF we've made progress on a number of drafts and have had two documents
approved for publication by the IESG (draft-ietf-l3vpn-ibgp & draft-ietf-l3vpn-mvpn-infra-addrs)
and another draft has passed WG last call and we will be submitting the PROTO writeup/publication
request for it shortly (draft-ietf-l3vpn-ospfv3-pece).

MANET (Joe) - One document went to last call, others getting ready. Main change is ability to carry
metrics. Then be ready for last call. An experimental document,resolving comments and getting an update.
Several mibs documents also. Another mib, more complicated, thinking to do as experimental.
A router to radio interface document also getting alot of debate. A requirements document will
be done first. Stewart asked on paws (white interface) work. Joe - we should bring it up on the
mailing list. Adrian- Ian will step down and we will be replacing.

MPLS (Ross) - Had two sessions, very busy, got thru agenda, 32 different drafts presented.
16 drafts submitted for publication, several heldup by normative reference to each other, now all going.
21 others are wg drafts. Slightly more than half related to mpls-tp. Some multipoint. Several individual
drafts which overlapped so asked to talk together. George added - most peaceful meeting had in awhile and
also got to do other work than mpls-tp.

OSPF (Acee) - OSPFv3 Authentication Trailer in IETF Last Call. Accepted WG document for OSPFv2
Authentication update to address KARP identified gaps when using manual keying. Accepted WG documents on
OSPFv2 prefix hiding, RFC 3137BIS (OSPFv2/OSPFv3 stub router support) and Routing IPv4 embedded packet
(aka, Address Family Border Router). Considering 3 drafts for reducing adjacencies on
broadcast/NBMA networks with unequal neighbor costs as WG documents. Considering accepting the OSPF TE
Express path TE draft as WG document. Intend to WG Last Call the OSPFv2 Interface Instance ID draft. 

PCE (Adrian) – Met earlier today, compact meeting. Only one chair here. Focused on drafts which
have been discussed on list. So alot of discussion at meeting also. No new rfcs. Their recharter
is on the next IESG meeting to review.

PIM (Adrian) - Met early this week. Nothing contentious. Were sucessfully rechartered. Updating
4601 and probably adopting the IGMP explicit tracking draft.

PWE3 (Andy) - PWE3 met on Tuesday afternoon. The WG has one new RFC since the last
IETF (RFC6240 - Circuit Emulation PW MIB), one in Auth48 (OAM message mapping)
and one in the RFC Ed's queue held on a mis-ref to an ANSI document (Fiber
Channel PW Encapsulation). There are also three new WG documents. There
was some debate on the use of the GAL in MPLS-TP, and we thought that it
was resolved, but the discussion has continued on the list. The meeting
discussed the status of some existing individual drafts including
rationalizing VCCV modes, PW status aggregation, and the use of LDP to
configure MPLS-TP OAM. There is still some debate as to whether the latter
is the right approach, or if this should be a management function. That
discussion is also continuing on the list though now looking like agreement.
New drafts were discussed on the use of MPLS-TP linear protection for PWs, and
policy control through a PW communities. The group also discussed a draft that had
initially been directed at MPLS, on T-LDP hello reduction, and concluded that this was
useful for PWE3.

ROLL (Adrian) - Meets tomorrow. Picked up a new recharter. Now have applicability statements
as deliverables which was asked by the IESG to show when/how to use ripple. Have first one as
a WG document.

RTGWG (Alia) - Met yesterday, new Co-Chair, Alvaro. Planning to recharter with fast reroute for multicast,
and milestones for composite link work. Framework document looks in good shape.

SIDR (Sandy) - 11 drafts in rfc editor queue, 2-3 more in last call comment, couple approaching
maturity level to allow last call. Discussion on list on several topics and had presentations, route
servers and their expectations to be transparent and v6, and another one on replay
protection.

VRRP (Adrian) - Put to rest. Mailing list exists for discussion of any topics. One draft will
move to AD sponsered instead of wg. Many thanks to the vrrp chairs for shepherding the wg
and completing the protocol. 

Stewart - errata. statistics kept on this, we were not the worse area in IETF. But now 3 more of the groups
are now in routing so our count is higher. So asking chairs to look at their errata so we can resolve.
On errata page, do search on wg, look at reported ones - those need to resolve.


GreenTE: Power-Aware Traffic Engineering (Beichuan)
----------------------------------------------------
Reviewed slides.

Acee - solution in 4693 can help with needing to handle periodic control messages such as ospf hello.
Acee - can see tunnels being less diversed but how have 30% more tunnels, this the new traffic moving?
Adrian - the total hasn't changed, just the old ones replaced by new ones.
John S. - have you looked at fast reroute techniques and how relate.
Beichuan - know about but haven't look at.
John - my concern when you turn off line cards on end of link not available for fast reroute, so
when need to do fast reroute, need these links so should think about.
Stewart - an interesting statistic you only obtain this if you don't do fast reroute. Also should
look at every time you do this regrooming, you reduce a flow e.g. a tdm pseudowire, this may need to do
a resync and that would be a service disruption for the end customer.
Adrian - if it was during a maintenance period maybe not.
Stewart - I think you should look at the dynamics also.
Alia - I think you should look at what happens during fast reroute, looking at the failures will add more
complexity. Can't compromise on reliability for power. You should also check if your network is still
connected.
Beichuan - it is still connected.
Alia - but if a failure it isn't.
Beichuan - we don't look at that. 
Curtis - good looking at, should look at where the power is being consumed. Don't just have a router on both
ends. Should look at what's between (amplifiers etc) and have parallel links - may take down a link but still
have the optical link amplifiers. So should look these. 
Beichuan - do you have any data? that a link still consumes powers even though turned off router interfaces?
Curtis - short haul doesn't consume much, but long haul does.
? - comment on putting more traffic on a link, if I put more traffic on a link, then it's that
more that i need to restore if a failure. So I don't necessarily double what's on a link.
Beichuan - we tried to minimize by keeping at 50% for failures. It will depend how much energy
want to save.
Adrian - don't consider the questions negative - this shows the level of interest is high.
Acee - I think also in the silicon area there is work going on.
Curtis - also power islands (can turn power off parts of a chip).


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