[Idr] IDR interim meeting on 2/8/2016 - Discussion of BGP FLow Specification -

"Susan Hares" <shares@ndzh.com> Mon, 08 February 2016 10:19 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AA71ACE5A for <idr@ietfa.amsl.com>; Mon, 8 Feb 2016 02:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.257
X-Spam-Level:
X-Spam-Status: No, score=-98.257 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, FH_RELAY_NODNS=1.451, GB_I_INVITATION=-2, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAqZxvFDWjdB for <idr@ietfa.amsl.com>; Mon, 8 Feb 2016 02:19:45 -0800 (PST)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF7B1ACE54 for <idr@ietf.org>; Mon, 8 Feb 2016 02:19:45 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.30;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Mon, 08 Feb 2016 05:19:28 -0500
Message-ID: <013201d1625a$31c0e980$9542bc80$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0133_01D16230.48F0FC00"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdFiV6ddedfGvEZZRBexctTrndvi+g==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/qglKo1YePLuBAn_S8taGrS114OU>
Cc: jgs@bgp.nu
Subject: [Idr] IDR interim meeting on 2/8/2016 - Discussion of BGP FLow Specification -
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 10:19:47 -0000

IDR Interim meeting  

Monday, February 8, 2016 

10:00 am  |  Eastern Standard Time (New York, GMT-05:00)  |  1 hr 30 mins 

 

Webex meeting: 

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

 

Meeting number:            644 895 386 

Meeting password:         yang.fun

 

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: 644 895 386

 

Agenda: 

 

0) Bash Agenda   [10:00 - 10:05 ]

1) BGP Flow Specification Version 2 [10:05 - 10:45]

   2 IDR WG drafts [draft-ietf-idr-flow-spec-v6, 

    draft=idr-flowspec-l2vpn] and 

   9 proposed drafts suggest additions to BGP Flow 

   specification.  On January 11, 2016 we had discussion

   of the issues of combining these drafts. 

   

   draft-hares-idr-flow-spec-combo describes: 

   a) issues relating to combination of drafts

   b) Precedence ordering for new BGP Flow Specification 

   c) Precedence among Routing Functions doing flow Filtering

   d) Yang models for BGP Flow Specification 

 

 

2) Discussion [10:45-11:30]

 

Questions to discuss: 

2-1)  Should we go toward a BGP Flow Specification version 2

with ordered filters and ordered actions? 

 

If so what format: 

a)      BGP Attribute 

b)      BGP NLRI with order + actions 

c)       BGP NLRI  + BGP Wide Communities  

d)      Another Format

 

2-2) Shall we Align all the Yang Modules for 

         Filter-Based RIBs (config (aka policy routing), BGP, I2RS) 

 

Drafts considered: 

Flow Specification RFCs: RFC5575, RFC7674

Drafts considered: 

- draft-hares-idr-flow-spec-combo

- draft-ietf-idr-flowspec-v6

- draft-ietf-idr-flowspec-l2vpn

- draft-eddy-idr-flowspec-packet-rate

- draft-eddy-idr-flowspec-exp

- draft-hao-idr-flowspec-nv03

- draft-hao-flowspec-redirect-tunnel 

- draft-li-idr-flowspec-rpd 

- draft-liag-idr-bgp-flowspec-label

- draft-liang-idr-flowspec-time

- draft-litkowski-idr-flowspec-interfaceset

- draft-vandevelde-idr-flowspec-path-redirect

 

From: IDR Working Group [mailto:messenger@webex.com] 
Sent: Monday, February 08, 2016 4:46 AM
To: idr-chairs@tools.ietf.org
Subject: (Forward to others) WebEx meeting invitation: BGP Flow Specification

 




You can forward this invitation to others. 

 


Hello, 


IDR Working Group invites you to join this WebEx meeting. 

 


 

 


BGP Flow Specification 


Monday, February 8, 2016 


10:00 am  |  Eastern Standard Time (New York, GMT-05:00)  |  1 hr 30 mins 

 


 

 


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

 


Meeting number: 

644 895 386 


Meeting password:

yang.fun

 


 

 


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: 644 895 386


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

 


 

 


 <https://ietf.webex.com/ietf/j.php?MTID=m53baa2248820f7f69022faf749f0ded8> Add this meeting to your calendar. (Cannot add from mobile devices.)

 


 

 


Can't join the meeting?  <https://ietf.webex.com/ietf/mc> Contact support. 

 


 

 


IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.