DR Working Group Interim 6/1/2015 [10:00 - 11:30am EDT]    
Agenda     
1) Agenda Bashing [10:00 - 10:05]            
2) BGP Wide communities [draft-raszuk-wide-bgp-communities] 
    Robert Raszuk [10:05 - 10:10] [Discussion: 10:10-10:20]
    http://datatracker.ietf.org/doc/draft-raszuk-wide-bgp-communities/ 

• [Sue]: The WG adoption call 
• [Robert]: Any feedback is welcome or use cases. 

    
3) BGP RTC [10:25-10:50)
    a) Chair overview of RTC choices [10:20-10:25]
    b) draft-litowski-idr-rtc-interas (Adoption 5/31 to 6/14) [10:25-10:35]
       [Jeff Haas]
       

•     Jeff Haas: The general advise is don't prune in specific cases.
• [Jeff review the problem statement in the slides]  
• Two cases exist and are discussed in the draft.  (see slides) 
• However in specific situations, the configuration can allow pruning.
• Stefano has captured the situation in the draft. 
• Jeff: In my opinoin would should pick one for the purposes of standardization,
• However. both are valid methods.  One issue is that Juniper and cisco
• deal with the pruning differently.
• Juniper prunes upon import (E-BGP and I-BGP)
• Cisco only on E-BGP.
• We should discuss this on the list. 
• Sue: This is a good idea. 

    c) Discussion [10:35-10:45]

    RTC drafts reviewed in Chair's slides 
    1) draft-ietf-rtc-no-rtc (WG LC 5/22 to 6/5 in progress)
        http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-no-rt/
    2) draft-litkowski-idr-rtc-interas (WG adoption call 5/31 to 6/14) 
        http://datatracker.ietf.org/doc/draft-litkowski-idr-rtc-interas/
    3)  draft-ietf-idr-legacy-rtc-05   (WG draft)
        http://datatracker.ietf.org/doc/draft-ietf-idr-legacy-rtc/
    4) draft-ietf-idr-rtc-hierarchical-rr-00 (WG draft)
        http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-hierarchical-rr/

4) BGP Link state model additions:  [10:45-11:10]

  a. draft-wang-idr-eag-distribution Update [Michael Wang] [10:45-10:55] 
  b. draft-previdi-idr-bgpls-segement-routing-epe-03 [Jie Dong] [10:55-11:05]
  Discussion: 

• Jie: draft-previdi-idr-bgpls-segment-routing-epe-03 
• uses the PeerSID instead of the Adj-SID (only for the Peer Segment). 

Additional notes from the -03 draft: 

• Peer SID - is Peer-Segment identifier  discussed in  section 4.3. 
•  Peer-SID: SID representing the peer of the BGP session.  
• The format is the same as defined for the Adj-SID in
• I-D.gredler-idr-bgp-ls-segment-routing-extension].  Suggested
•  codepoint value: 1036
• Peer-Set-SID: the SID representing the group the peer is part of.
• The format is the same as defined for the Adj-SID in
•  [I-D.gredler-idr-bgp-ls-segment-routing-extension]. 
• Suggested codepoint value: 1037
• Note:  Peer-SID MUST be present when BGP-LS is used for the use case
•   when BGPLS is used for the use case described in
•     described in [I-D.filsfils-spring-segment-routing-central-epe] and
• It may be  MAY be omitted for other use cases.

    c. Discussion of Acee's suggestion [11:05-11:15]

• [Sue]: Our plan is to coordinate OSPF, ISIS, and BGP 

  
  Existing ls drafts are:
    1) draft-ietf-idr-ls-distribution-10 (In IESG processing)
    2) draft-ietf-idr-ls-distribution-impl-04 (IESG wants No draft, but wiki input)
    3) draft-ietf-idr-te-lsp-distribution-03 (WG draft )
 
    Proposed additions are:
   1) draft-wang-idr-eag-distribution (WG Adoption 5/20 to 6/3)
    2) draft-previdi-idr-bgpls-segment-routing-epe-03(WG Adoption 5/31 to 6/14)
    3) draft-psarkar-idr-bgp-ls-node-admin-tag-extension-00 (no request for adoption)
    4) draft-­‐zhuang-­‐idr-­‐bgp-­‐ls-­‐sbfd-­‐extensions-­‐00 (no request for adoption) 
    
     Acee suggestlast week on simplifying ISIS/IGP additions
     to draft-idr-ls-distribution.  Should we? 
      (http://www.ietf.org/mail-archive/web/idr/current/msg14425.html)                 
    
    Discussion: 
        Sue: Any objections to use Acee's suggestion for OSPF and ISIS bgp-ls work? 
        [Silence] 
       
    5) BGP I2RS Use Case
        draft-keyupate-idr-i2rs-bgp-usecases-00.txt [Sue Hares] [11:15-11:30]
        Discussion: 
            [no comments] 
        
Web ex: https://ietf.webex.com/ietf/j.php?MTID=m689576316eaf19b397fbe242a310725f
Meeting number: 649 193 591         
Meeting password:   john.knows.all        
1-877-668-4493 Call-in toll free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)        
IDR Minutes:         http://etherpad.tools.ietf.org:9000/p/idr-interim-06-01-2015-Minutes                
IDR Interim Virtual Blue Sheets        http://etherpad.tools.ietf.org:9000/p/idr-interim-6-01-2015-vBlueSheets                
Proceedings: 

Next Interims: 6/15 (Yang models) and 6/29 (Route Server, Tools, Yang, and nexthop)