[i2rs] IDR interim on 1/11/2016 at 10:00-11:30am: Topic: Adding new Flow Specification drafts

["Susan Hares" <[e-mail]>]

IDR WG: 

 

Topic: Add new Flow Specification Drafts

 

Agenda: 

 

10:00 –10:05:   Agenda Bashing  

10:05 - 10:25:   Presentation on strawman for combing flow specification 

10:25 – 10:45:  Discussion of Strawman 

10:45 – 11:05:  Comparison of I2RS Filter-Based RIB and Flow Specification Data,

                                And why this matters to Flow Specification Yang model 

11:05 – 11:25   Discussion  

11:25 – 11:30   Closing discussion 

 

IDR interim: Monday January 11, 2016 

10:00 am – 11:30am 1.5 hours 

Meeting number:                645 542 511 

Meeting password:              9Wuad3DF

 


IDR interim 1/11 


Monday, January 11, 2016 


10:00 am  |  Eastern Standard Time (New York, GMT-05:00)  |  1.5 hrs 

 


 

 


 <https://ietf.webex.com/ietf/j.php?MTID=mfdc40e83b09b3cc9fb2d4001a9a417d2> Join WebEx meeting 


https://ietf.webex.com/ietf/j.php?MTID=mfdc40e83b09b3cc9fb2d4001a9a417d2

 


Meeting number: 

645 542 511 


Meeting password:

9Wuad3DF

 


 

 


Join by phone


1-877-668-4493 Call-in toll free number (US/Canada)


1-650-479-3208 Call-in toll number (US/Canada)


Access code: 645 542 511


 <http://www.webex.com/pdf/tollfree_restrictions.pdf> Toll-free calling restrictions

 

 

 

Introduction to Meeting 

 

The Topic  for IDR interim on 1/11/2016 is a discussion on the addition of new flow specifications proposed by the drafts listed below to the RFC5575 (flow specification), RFC7674 (redirect clarification), draft-ietf-idr-flowspec-v6-03, and IDR WG draft ietf-idr-flowspec-l2vpn-03.txt.       The existing flow specification specify the filter conditions and actions (in BGP extended community) that occur when a router receives a IP packet (IPv4 and IPv6) or a L2VPN MAC frame. A short form of this is:

Event = packet reception (specified by local configuration) 

Match conditions in NLRI form (24 existing, 5 new)  

-          12 IPv4 RFC5575 and IPv6 (draft-ietf-idr-flowspec-v6-03.txt) 

-          1 IPv6 only - draft-ietf-idr-flowspec-v6-03, 

-          11 in draft-ietf-idr-flowspec-l2vpn-03.txt

-           5 in new drafts (3 nvo3 related, 1 time) 

-           Two additional MPLS possible  – MPLS label, MPLS label stack 

 

Action: in Extended communities 

-          (1) Traffic rate limit by bytes (RFC5575), 

-          (1) Traffic rate limit by packets (draft-eddy-idr-flowspec-packet rate)

-          (1) Traffic remark (in DSCP) (RFC5575)  

-          (3) Redirect to IP-VPN (RFC5575, RFC7674) – 3 forms 

-          (1) Redirect to tunnel (draft-hao-flowspec-redirect-tunnel-00.txt) 

-          (1) NV03 Delimiter (draft-hao-flowspec-nv03-03.txt) 

-          (1) VLAN Action (draft-hao-flowspec-nv03-03.txt) 

-          (1) TPID action (draft-hao-flowspec-nv03-03.txt) 

-          (1) label action (draft-liang-bgp-flowspec-label-01.txt) 

-          (1) interface set action (draft-litowski-idr-flowspec-interfaceset-03) – ACL + flowspec + interface-group 

-          (1) Traffic Action - Flow processing flags (Flags: stop with this filter(S), Sample/log this filter) 

-          (1) Put additional actions or filters in a BGP attribute (draft-li-idr-flowspec-rpd-00)

      (Add flag R to Traffic Action allow new filters/Attributes to be carried in BGP attribute) 

(1)    [proposal] Add flag to Traffic Action that states [C- combination of Flow specification using rules] 

If 1, then rules apply.  If zero, only RFC5575 and RFC7674 rules apply.  

 

 

Drafts Discussed in meeting: 

1: draft-hao-idr-flowspec-redirect-tunnel-00.txt 

https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-redirect-tunnel/

 

2: draft-hao-idr-flowspec-nv03-0

https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-nvo3

 

3: draft-litowski-idr-flowspec-interfaceset-03 

https://datatracker.ietf.org/doc/draft-litkowski-idr-flowspec-interfaceset/ <https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-nvo3> 

 

4: draft-liang-idr-flowspec-label

https://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-label/

 

5. draft-liang-idr-bgp-flowspec-time 

https://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-time/

 

6. draft –li-idr-flowspec-rpd-00

http://datatracker.ietf.org/doc/



7. draft-eddy-idr-flowspec-packet-rate—00 

https://datatracker.ietf.org/doc/draft-eddy-idr-flowspec-packet-rate/

 

8. draft-vandevelde-idr-flowspec-path-redirect-00 

https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/

 

 

Drafts related to “Why” indirect pointers to application flows are valuable

Specifying why indirect segment pointer is valuable

1.       draft-li-spring-segment-path-programming

 

 

For Second discussion on I2RS 

1: Yang module for I2RS-Flow Specification Discussion 

    https://datatracker.ietf.org/doc/draft-wu-idr-flowspec-yang-cfg/

 

2: I2RS FB-RIB 

https://datatracker.ietf.org/doc/draft-hares-i2rs-fb-rib-data-model/

https://datatracker.ietf.org/doc/draft-kini-i2rs-fb-rib-info-model/

 

3: Extensions to Flow specification 

Draft-eddy-idr-flowspec-exp-00 

-          flow delegation 

-          flow specification feedback (time, flowspec ID, start/stop flow specs, etc). 

-          enhanced flow-spec validation 

-          Flow-specification identifier 

-          Crypto-graphic check using BGP-SEC 

-          ROA checks on flow-spec delegation