IS-IS WG at IETF-81 Quebec City Monday 15:10 - 16:10, Room 202 WG Chair - Chris Hopps, Dave Ward. Notetaker - Acee Lindem, acee.lindem@ericsson.com Document Status - See Slides - 4 New RFCs! - 2 in RFC Ed Queue including IETF 802.1aq - 2 New WG Documents - 6 Drafts in 802.1aq/Shortest Path Bridging - Paul Unbehagen, ALU - See Slides - Cooperation between IEEE 802.1 and IETF IS-IS WG - This was 3rd Interop with 187 nodes with 412 links - 4th Interop in a few months - Based on lasted IETF draft -05, focused on SPBM - Tested all SPB TLVs in Interop - Next will interop will include MIBs and bridge priority support - Informational Draft will be produced with recommended defaults for 802.1aq and to use ISIS hostname. - Tata will host 4th Interop in NJ with transatlantic link - Will focus on more extensie 802.1aq and MIBs. Wenhu Lu: How will this scale with VPLS? Paul: Nothing preventing you from using SPB in conjunction with VPLS. SPB is solely a control plane for existing data planes. Wenhu: Digest used for determining if network has changed. Does this slow down convergence? Paul: Digest is optional hello element. It not required for convergence but may be used for loop detection. Dave Allen: The digest is premised on agreeing on digest implies agreement to the root and distance to the root. VPLS - since SPB is not constrained to single link, it can provide upstream resilency. Florin Balus: Agrees with Dave. Should be draft on interoperabilty between VPLS and SPB. Could be extended to BGP interop. Donald Eastlake: RPF Check requires information not previously required by any bridging specification. Hence, existing switches could require an upgrade Overlay Transport Virtualization - Dhananjaya Rao, Cisco - See slides. Floren: What is this solution providing? Dhananjaya: Transparent LAN solution Chris: OTV solution itself will be presented in the RTGWG. Floren: How does this compare to other transparent LAN solutions? Dhananjaya: The differentiator is that it is protocol agnostic. Floren: Overlapp with TRILL and BGP/VPLS solutions. Dhananjaya: Will be presented in RTGWG Floren: Should be be presented in L2VPN as well. Dave Allen: Where is this draft and the base draft going? Dhananjay: We intend to informational. Dave Allen: You will need IANA. Stewart Bryant: L2VPN is SP specific while this is Over-The-Top and would be a better fit in RTGWG and will be presented. Floren: There IS overlapp in the data center. Possible use of TRILL Use of GENAPPP, Donald Eastlake, Huawei - See slides. Les Ginsberg - GENAPP was invented as a way to get extraneous data out of the base instance of IS-IS. Donald: I don't particularly care if the information is in GENAPP or in a Router Capabilities sub-TLV. TRILL uses the RBridge channel for OAM. This is to advertise what RBridge channel protocols are supported. Les: What would happen if you didn't support this? Donald: Depending on details, OAM packets intended for RBridges would be spewed out multiple ports multicast to end stations. Les: No different than advertising what ports are supported? GENAPP was invented to use IS-IS as a generic multicast flooding protocol. Is this a routing function? Donald: What RBridge channel protocols are supported is not a core IS-IS routing function but it is part of the TRILL protocol. IS-IS is commonly used to advertise information that is not part of core IS-IS routing. For example, the TRILL version number is provided. Steward Bryant: I'm worried about the proliferation of OAM protocols. MPLS has a generic OAM channel being extended towards Ethernet OAM. This TRILL OAM should copy the MPLS OAM and use the same channels. Donald: Does MPLS OAM provide an illegal egress nickname or a Hop Count expired return code? There are a variety of OAM, particularly ICMP like things, specific to TRILL. TRILL can support BFD Echo which is not provided by MPLS OAM. Stewart: There may be unique elements to TRILL but the like elements of OAM should be common. Chris: Dave will be proud we ended on a prime number of minutes - 59!