From adrian@olddog.co.uk Fri Jan 11 13:10:55 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61DB21F8ACE; Fri, 11 Jan 2013 13:10:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.554 X-Spam-Level: X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hL-iEZ67fLul; Fri, 11 Jan 2013 13:10:53 -0800 (PST) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 5948A21F8AC8; Fri, 11 Jan 2013 13:10:50 -0800 (PST) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BLAmOk032164; Fri, 11 Jan 2013 21:10:48 GMT Received: from 950129200 (089144192150.atnat0001.highway.a1.net [89.144.192.150]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BLAj8v032133 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Jan 2013 21:10:47 GMT From: "Adrian Farrel" To: , , , , Subject: FW: Last Call: (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC Date: Fri, 11 Jan 2013 21:10:47 -0000 Message-ID: <01cb01cdf040$2219c5e0$664d51a0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac3wPqAVHt9RLqNORBmXnogF2kx3kQ== Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 21:10:55 -0000 Heads up. A lot of you will be interested in this. Comments as usual for IETF last calls (see the instructions embedded). Do not send your comments in reply to *this* message. Thanks, Adrian > Sent: 11 January 2013 19:36 > To: IETF-Announce > Cc: opsawg@ietf.org > Subject: Last Call: (An > Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) > to Informational RFC > > > The IESG has received a request from the Operations and Management Area > Working Group WG (opsawg) to consider the following document: > - 'An Overview of Operations, Administration, and Maintenance (OAM) > Mechanisms' > as Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2013-01-25. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > Operations, Administration, and Maintenance (OAM) is a general term > that refers to a toolset that can be used for fault detection and > isolation, and for performance measurement. OAM mechanisms have been > defined for various layers in the protocol stack, and are used with a > variety of protocols. > > This document presents an overview of the OAM mechanisms that have > been defined and are currently being defined by the IETF. > > > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/ > > > No IPR declarations have been submitted directly on this I-D. > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg From adrian@olddog.co.uk Wed Jan 16 08:22:08 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC8EB21F8B25 for ; Wed, 16 Jan 2013 08:22:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.564 X-Spam-Level: X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTWQkD7L5nv8 for ; Wed, 16 Jan 2013 08:22:07 -0800 (PST) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3BB21F8B19 for ; Wed, 16 Jan 2013 08:22:04 -0800 (PST) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0GGM242027714 for ; Wed, 16 Jan 2013 16:22:02 GMT Received: from 950129200 (089144192153.atnat0001.highway.a1.net [89.144.192.153]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0GGLqTG027661 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 16 Jan 2013 16:21:59 GMT From: "Adrian Farrel" To: References: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> In-Reply-To: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> Subject: FW: WG Review: Interface to the Routing System (i2rs) Date: Wed, 16 Jan 2013 16:21:52 -0000 Message-ID: <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQD0yAf0rC+0X2BpFjekKSQhiMk8EZn+dYlw Content-Language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 16:22:08 -0000 FYI > -----Original Message----- > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] On Behalf Of The IESG > Sent: 15 January 2013 16:43 > To: IETF-Announce > Subject: WG Review: Interface to the Routing System (i2rs) > > A new IETF working group has been proposed in the Routing Area. The IESG > has not made any determination yet. The following draft charter was > submitted, and is provided for informational purposes only. Please send > your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22. > > Interface to the Routing System (i2rs) > ------------------------------------------------ > Current Status: Proposed Working Group > > Assigned Area Director: > Adrian Farrel > > Mailing list > Address: i2rs@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs > Archive: > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html > > Charter of Working Group: > > Working Group Name: > Interfaces to the Routing System (I2RS) > > IETF Area: > Routing Area > > Chair(s): > TBD > Routing Area Director(s): > Adrian Farrel > Routing Area Advisor: > Adrian Farrel > Operations Area Advisor: > TBD > > Mailing Lists: > General Discussion: i2rs@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs > Archive: > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html > > Description of Working Group: > > In an IP routed network, the routing system: > > - Distributes topology and other state (network metadata) > - Uses this network metadata to determine the best path to each given > reachable destination attached to the network > - Communicates these decisions to the forwarding plane of each > forwarding device in the network. > > That is, the routing system is the collection of entities, protocols > and processes that collectively build the forwarding tables that are > exported into the entities that constitute the network's fowarding > plane. > > While processes participating in the routing system are often colocated > with the local forwarding elements, this isn't a necessary condition. > Thus, the routing system includes control plane protocols that compute > routes and paths for data packets, wherever the processes implementing > those protocols may be running. > > I2RS facilitates real-time or event driven interaction with the routing > system through a collection of protocol-based control or management > interfaces. These allow information, policies, and operational > parameters to be injected into and retrieved (as read or by > notification) from the routing system while retaining data consistency > and coherency across the routers and routing infrastructure, and among > multiple interactions with the routing system. The I2RS interfaces will > co-exist with existing configuration and management systems and > interfaces. > > It is envisioned that users of the I2RS interfaces will be management > applications, network controllers, and user applications that make > specific demands on the network. > > The I2RS working group works to develop a high-level framework and > architecture that describes the basic building-blocks necessary to > enable the specific use cases, and that will lead to an understanding > of the abstract informational models and requirements for > encodings and protocols for the I2RS interfaces. Small and well-scoped > use cases are critical to constrain the scope of the work and achieve > sufficient focus for the working group to deliver successful outcomes. > Initial work within the working group will be limited to a single > administrative domain. > > The working group is chartered to work on the following items: > > - High-level architecture and framework for I2RS including > considerations of policy and security. > > - Tightly scoped key use cases for operational use of I2RS as follows: > o Interactions with the Routing Information Base (RIB). Allowing > read and write access to the RIB, but no direct access to the > Forwarding Information Base (FIB). > o Control and analysis of the operation of the Border gateway > Protocol (BGP) including the setting and activation of policies > related to the protocol. > o Control, optimization, and choice of traffic exit points from > networks based on more information than provided by the dynamic > control plane. > o Distributed reaction to network-based attacks through quickly > modification of the control plane behavior to reroute traffic for > one destination while leaving a standard mechanisms (filters, > metrics, and policy) in place for other routes. > o Service layer routing to improve on existing hub-and-spoke > traffic. > o The ability to extract information about topology from the > network. Injection and creation of topology will not be considered > as an initial work item. > > Other use cases may be adopted by the working group only through > rechartering. > > - Abstract information models consistent with the use cases. > > - Requirements for I2RS protocols and encoding languages. > > - An analysis of existing IETF and other protocols and encoding > languages against the requirements. > > The working group is not currently chartered to develop protocols, > encoding languages, or data models. The objective of this work effort > is to arrive at common standards for these items, but these items are > dependent on the progress of the topics listed above. Work for these > items will be conducted in this working group only after a re-charter, > and/or may be carried out in another working group with specific > responsibility for the protocol or encoding language. > > Goals and Milestones: > > Jul 2013: Request publication of an Informational document defining the > problem statement > Jul 2013: Request publication of an Informational document defining the > highlevel architecture and framework > Aug 2013: Request publication of Informational documents describing use > cases > Sep 2013: Request publication of an Informational document defining the > protocol requirements > Sep 2013: Request publication of an Informational document defining > encoding language requirements > Nov 2013: Request publication of Standards Track documents specifying > information models > Nov 2013: Request publication of an Informational document providing an > analysis of existing IETF and other protocols and encoding > languages against the requirements > Dec 2013: Consider re-chartering > From karim.benhamouche@ovnetworks.com Wed Jan 16 11:04:41 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5346021F88B9 for ; Wed, 16 Jan 2013 11:04:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NAX2e4W+OrF for ; Wed, 16 Jan 2013 11:04:40 -0800 (PST) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6B83821F88A9 for ; Wed, 16 Jan 2013 11:04:39 -0800 (PST) Received: by mail-la0-f41.google.com with SMTP id em20so1810866lab.14 for ; Wed, 16 Jan 2013 11:04:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=AdYF+9Nst5StK8OcxazR/6LnleQXbPJ/+4JzL2ub9ck=; b=epzmqS34FfnpDc2LjmI5f0pWks5eR4w8KhzcNfwPKJ3rKPSeY8ixSITl3idwr4chqv QaW1KldNneSK8hzTUQEClG2kEg+VCohyjNMLgz3KGpyUMeXY/BT8/GfSrhONHIouZpO2 4NgC6Jw24dzDHEig8lj8X7XRDAJy2gvtwJAZqaIV8J4avLHQFKKEv7Jd4xeg+wIRQ8Yi Gp9uyWmzHTRYKQiz1Eco1pZvyd5505yD5AV3vnhLOo3pf/MK9HeDWPQG05pboVhEYVQI ZjFxFM8aZZpQIMWQrROzuOC1gC2lElzIkGlq9iG7FuNfRNPVuqbPbBuftA2w5mQiLXrG iqyw== MIME-Version: 1.0 X-Received: by 10.152.124.15 with SMTP id me15mr2268349lab.5.1358363078205; Wed, 16 Jan 2013 11:04:38 -0800 (PST) Received: by 10.112.101.4 with HTTP; Wed, 16 Jan 2013 11:04:38 -0800 (PST) X-Originating-IP: [184.144.110.53] In-Reply-To: <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> References: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> Date: Wed, 16 Jan 2013 14:04:38 -0500 Message-ID: Subject: Re: FW: WG Review: Interface to the Routing System (i2rs) From: karim benhamouche To: adrian@olddog.co.uk Content-Type: multipart/alternative; boundary=f46d04374581c0a28204d36c8c81 X-Gm-Message-State: ALoCoQli8kAXISqSTZ/ZH6svUSt2+MgXJ3xF/ER35hYxpGeWhcAXHqJjSGoCIu7XCqKNd9S2wspe Cc: routing-discussion@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 19:04:41 -0000 --f46d04374581c0a28204d36c8c81 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Adrian, Is it related to SDN ? ------------------------------------------------------ *Karim Benhamouche, CCIE #24645 * Sr. IP Network Specialist and CEO Sp=E9cialiste S=E9nior en R=E9seaux IP et Pr=E9sident Montreal: (514) 371-0734 / Toronto: (647) 874-5544 Email / Courriel: karim.benhamouche@ovnetworks.com On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel wrote= : > FYI > > > -----Original Message----- > > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > > bounces@ietf.org] On Behalf Of The IESG > > Sent: 15 January 2013 16:43 > > To: IETF-Announce > > Subject: WG Review: Interface to the Routing System (i2rs) > > > > A new IETF working group has been proposed in the Routing Area. The IES= G > > has not made any determination yet. The following draft charter was > > submitted, and is provided for informational purposes only. Please send > > your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22= . > > > > Interface to the Routing System (i2rs) > > ------------------------------------------------ > > Current Status: Proposed Working Group > > > > Assigned Area Director: > > Adrian Farrel > > > > Mailing list > > Address: i2rs@ietf.org > > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs > > Archive: > > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html > > > > Charter of Working Group: > > > > Working Group Name: > > Interfaces to the Routing System (I2RS) > > > > IETF Area: > > Routing Area > > > > Chair(s): > > TBD > > Routing Area Director(s): > > Adrian Farrel > > Routing Area Advisor: > > Adrian Farrel > > Operations Area Advisor: > > TBD > > > > Mailing Lists: > > General Discussion: i2rs@ietf.org > > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs > > Archive: > > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html > > > > Description of Working Group: > > > > In an IP routed network, the routing system: > > > > - Distributes topology and other state (network metadata) > > - Uses this network metadata to determine the best path to each given > > reachable destination attached to the network > > - Communicates these decisions to the forwarding plane of each > > forwarding device in the network. > > > > That is, the routing system is the collection of entities, protocols > > and processes that collectively build the forwarding tables that are > > exported into the entities that constitute the network's fowarding > > plane. > > > > While processes participating in the routing system are often colocate= d > > with the local forwarding elements, this isn't a necessary condition. > > Thus, the routing system includes control plane protocols that compute > > routes and paths for data packets, wherever the processes implementing > > those protocols may be running. > > > > I2RS facilitates real-time or event driven interaction with the routin= g > > system through a collection of protocol-based control or management > > interfaces. These allow information, policies, and operational > > parameters to be injected into and retrieved (as read or by > > notification) from the routing system while retaining data consistency > > and coherency across the routers and routing infrastructure, and among > > multiple interactions with the routing system. The I2RS interfaces wil= l > > co-exist with existing configuration and management systems and > > interfaces. > > > > It is envisioned that users of the I2RS interfaces will be management > > applications, network controllers, and user applications that make > > specific demands on the network. > > > > The I2RS working group works to develop a high-level framework and > > architecture that describes the basic building-blocks necessary to > > enable the specific use cases, and that will lead to an understanding > > of the abstract informational models and requirements for > > encodings and protocols for the I2RS interfaces. Small and well-scoped > > use cases are critical to constrain the scope of the work and achieve > > sufficient focus for the working group to deliver successful outcomes. > > Initial work within the working group will be limited to a single > > administrative domain. > > > > The working group is chartered to work on the following items: > > > > - High-level architecture and framework for I2RS including > > considerations of policy and security. > > > > - Tightly scoped key use cases for operational use of I2RS as follows: > > o Interactions with the Routing Information Base (RIB). Allowing > > read and write access to the RIB, but no direct access to the > > Forwarding Information Base (FIB). > > o Control and analysis of the operation of the Border gateway > > Protocol (BGP) including the setting and activation of policies > > related to the protocol. > > o Control, optimization, and choice of traffic exit points from > > networks based on more information than provided by the dynamic > > control plane. > > o Distributed reaction to network-based attacks through quickly > > modification of the control plane behavior to reroute traffic for > > one destination while leaving a standard mechanisms (filters, > > metrics, and policy) in place for other routes. > > o Service layer routing to improve on existing hub-and-spoke > > traffic. > > o The ability to extract information about topology from the > > network. Injection and creation of topology will not be considere= d > > as an initial work item. > > > > Other use cases may be adopted by the working group only through > > rechartering. > > > > - Abstract information models consistent with the use cases. > > > > - Requirements for I2RS protocols and encoding languages. > > > > - An analysis of existing IETF and other protocols and encoding > > languages against the requirements. > > > > The working group is not currently chartered to develop protocols, > > encoding languages, or data models. The objective of this work effort > > is to arrive at common standards for these items, but these items are > > dependent on the progress of the topics listed above. Work for these > > items will be conducted in this working group only after a re-charter, > > and/or may be carried out in another working group with specific > > responsibility for the protocol or encoding language. > > > > Goals and Milestones: > > > > Jul 2013: Request publication of an Informational document defining the > > problem statement > > Jul 2013: Request publication of an Informational document defining the > > highlevel architecture and framework > > Aug 2013: Request publication of Informational documents describing use > > cases > > Sep 2013: Request publication of an Informational document defining the > > protocol requirements > > Sep 2013: Request publication of an Informational document defining > > encoding language requirements > > Nov 2013: Request publication of Standards Track documents specifying > > information models > > Nov 2013: Request publication of an Informational document providing an > > analysis of existing IETF and other protocols and encoding > > languages against the requirements > > Dec 2013: Consider re-chartering > > > > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www.ietf.org/mailman/listinfo/routing-discussion > --f46d04374581c0a28204d36c8c81 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Adrian,

Is it related to SDN ?=



----------------------------------------= --------------
Karim Benhamouche, CC= IE #24645
Sr. IP Network Special= ist and CEO
Sp=E9cialiste S=E9nior en R=E9seaux IP et=A0Pr=E9sident
Montreal: (514) 371-0734 / Toronto: (647) 874-5544
Email / Courriel:=A0karim.benhamouche@ovnetworks.com=


On Wed, Jan 16, 2013 at 11:21 AM, Adrian= Farrel <adrian@olddog.co.uk> wrote:
FYI

> -----Original Message-----
> From: ietf-announce-= bounces@ietf.org [mailto:ietf-announc= e-
> bounces@ietf.org] On Behalf Of= The IESG
> Sent: 15 January 2013 16:43
> To: IETF-Announce
> Subject: WG Review: Interface to the Routing System (i2rs)
>
> A new IETF working group has been proposed in the Routing Area. The IE= SG
> has not made any determination yet. The following draft charter was > submitted, and is provided for informational purposes only. Please sen= d
> your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22.
>
> Interface to the Routing System (i2rs)
> ------------------------------------------------
> Current Status: Proposed Working Group
>
> Assigned Area Director:
> =A0 Adrian Farrel <adrian@ol= ddog.co.uk>
>
> Mailing list
> =A0 Address: i2rs@ietf.org
> =A0 To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs
> =A0 Archive:
> http://www.ietf.org/mail-archive/web/i2rs/current/m= aillist.html
>
> Charter of Working Group:
>
> Working Group Name:
> =A0 =A0 =A0 =A0 Interfaces to the Routing System (I2RS)
>
> IETF Area:
> =A0 =A0 =A0 =A0 Routing Area
>
> Chair(s):
> =A0 =A0 =A0 =A0 TBD
> Routing Area Director(s):
> =A0 =A0 =A0 =A0 Adrian Farrel
> Routing Area Advisor:
> =A0 =A0 =A0 =A0 Adrian Farrel
> Operations Area Advisor:
> =A0 =A0 =A0 =A0 TBD
>
> Mailing Lists:
> =A0 =A0 =A0 =A0 General Discussion: i= 2rs@ietf.org
> =A0 =A0 =A0 =A0 To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs=
> =A0 =A0 =A0 =A0 Archive:
> http://www.ietf.org/mail-archive/web/i2rs/current/m= aillist.html
>
> Description of Working Group:
>
> =A0In an IP routed network, the routing system:
>
> =A0- Distributes topology and other state (network metadata)
> =A0- Uses this network metadata to determine the best path to each giv= en
> =A0 =A0reachable destination attached to the network
> =A0- Communicates these decisions to the forwarding plane of each
> =A0 =A0forwarding device in the network.
>
> =A0That is, the routing system is the collection of entities, protocol= s
> =A0and processes that collectively build the forwarding tables that ar= e
> =A0exported into the entities that constitute the network's foward= ing
> =A0plane.
>
> =A0While processes participating in the routing system are often coloc= ated
> =A0with the local forwarding elements, this isn't a necessary cond= ition.
> =A0Thus, the routing system includes control plane protocols that comp= ute
> =A0routes and paths for data packets, wherever the processes implement= ing
> =A0those protocols may be running.
>
> =A0I2RS facilitates real-time or event driven interaction with the rou= ting
> =A0system through a collection of protocol-based control or management=
> =A0interfaces. These allow information, policies, and operational
> =A0parameters to be injected into and retrieved (as read or by
> =A0notification) from the routing system while retaining data consiste= ncy
> =A0and coherency across the routers and routing infrastructure, and am= ong
> =A0multiple interactions with the routing system. The I2RS interfaces = will
> =A0co-exist with existing configuration and management systems and
> =A0interfaces.
>
> =A0It is envisioned that users of the I2RS interfaces will be manageme= nt
> =A0applications, network controllers, and user applications that make<= br> > =A0specific demands on the network.
>
> =A0The I2RS working group works to develop a high-level framework and<= br> > =A0architecture that describes the basic building-blocks necessary to<= br> > =A0enable the specific use cases, and that will lead to an understandi= ng
> =A0of the abstract informational models and requirements for
> =A0encodings and protocols for the I2RS interfaces. Small and well-sco= ped
> =A0use cases are critical to constrain the scope of the work and achie= ve
> =A0sufficient focus for the working group to deliver successful outcom= es.
> =A0Initial work within the working group will be limited to a single > =A0administrative domain.
>
> =A0The working group is chartered to work on the following items:
>
> =A0- High-level architecture and framework for I2RS including
> =A0 =A0considerations of policy and security.
>
> =A0- Tightly scoped key use cases for operational use of I2RS as follo= ws:
> =A0 =A0 o Interactions with the Routing Information Base (RIB). Allowi= ng
> =A0 =A0 =A0 read and write access to the RIB, but no direct access to = the
> =A0 =A0 =A0 Forwarding Information Base (FIB).
> =A0 =A0 o Control and analysis of the operation of the Border gateway<= br> > =A0 =A0 =A0 Protocol (BGP) including the setting and activation of pol= icies
> =A0 =A0 =A0 related to the protocol.
> =A0 =A0 o Control, optimization, and choice of traffic exit points fro= m
> =A0 =A0 =A0 networks based on more information than provided by the dy= namic
> =A0 =A0 =A0 control plane.
> =A0 =A0 o Distributed reaction to network-based attacks through quickl= y
> =A0 =A0 =A0 modification of the control plane behavior to reroute traf= fic for
> =A0 =A0 =A0 one destination while leaving a standard mechanisms (filte= rs,
> =A0 =A0 =A0 metrics, and policy) in place for other routes.
> =A0 =A0 o Service layer routing to improve on existing hub-and-spoke > =A0 =A0 =A0 traffic.
> =A0 =A0 o The ability to extract information about topology from the > =A0 =A0 =A0 network. Injection and creation of topology will not be co= nsidered
> =A0 =A0 =A0 as an initial work item.
>
> =A0 =A0 Other use cases may be adopted by the working group only throu= gh
> =A0 =A0 rechartering.
>
> =A0- Abstract information models consistent with the use cases.
>
> =A0- Requirements for I2RS protocols and encoding languages.
>
> =A0- An analysis of existing IETF and other protocols and encoding
> =A0 =A0languages against the requirements.
>
> =A0The working group is not currently chartered to develop protocols,<= br> > =A0encoding languages, or data models. The objective of this work effo= rt
> =A0is to arrive at common standards for these items, but these items a= re
> =A0dependent on the progress of the topics listed above. Work for thes= e
> =A0items will be conducted in this working group only after a re-chart= er,
> =A0and/or may be carried out in another working group with specific > =A0responsibility for the protocol or encoding language.
>
> Goals and Milestones:
>
> Jul 2013: Request publication of an Informational document defining th= e
> =A0 =A0 =A0 =A0 =A0 problem statement
> Jul 2013: Request publication of an Informational document defining th= e
> =A0 =A0 =A0 =A0 =A0 highlevel architecture and framework
> Aug 2013: Request publication of Informational documents describing us= e
> =A0 =A0 =A0 =A0 =A0 cases
> Sep 2013: Request publication of an Informational document defining th= e
> =A0 =A0 =A0 =A0 =A0 protocol =A0requirements
> Sep 2013: Request publication of an Informational document defining > =A0 =A0 =A0 =A0 =A0 encoding language requirements
> Nov 2013: Request publication of Standards Track documents specifying<= br> > =A0 =A0 =A0 =A0 =A0 information models
> Nov 2013: Request publication of an Informational document providing a= n
> =A0 =A0 =A0 =A0 =A0 analysis of existing IETF and other protocols and = encoding
> =A0 =A0 =A0 =A0 =A0 languages against the requirements
> Dec 2013: Consider re-chartering
>


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org<= /a>
https://www.ietf.org/mailman/listinfo/routing-discussion

--f46d04374581c0a28204d36c8c81-- From adrian@olddog.co.uk Wed Jan 16 12:44:12 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B85311E80A2 for ; Wed, 16 Jan 2013 12:44:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.561 X-Spam-Level: X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STYzja96a6LH for ; Wed, 16 Jan 2013 12:44:10 -0800 (PST) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 09F6C21F8667 for ; Wed, 16 Jan 2013 12:44:09 -0800 (PST) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0GKi44P027341; Wed, 16 Jan 2013 20:44:04 GMT Received: from 950129200 (089144192153.atnat0001.highway.a1.net [89.144.192.153]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0GKhrIu027311 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Jan 2013 20:43:56 GMT From: "Adrian Farrel" To: "'karim benhamouche'" References: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> In-Reply-To: Subject: RE: FW: WG Review: Interface to the Routing System (i2rs) Date: Wed, 16 Jan 2013 20:43:52 -0000 Message-ID: <01e501cdf42a$34bdf340$9e39d9c0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E6_01CDF42A.34C2AE30" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQD0yAf0rC+0X2BpFjekKSQhiMk8EQIvfYj8AfhxweWZ3YSq4A== Content-Language: en-gb Cc: routing-discussion@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 20:44:12 -0000 This is a multipart message in MIME format. ------=_NextPart_000_01E6_01CDF42A.34C2AE30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Karim, What can I say? RTFM. Well, read the draft charter, and read the I-Ds that exist. You can find the I-Ds by searching for "-irs-" in the datatracker. Also read the slides from the BoF in Atlanta. Cheers, Adrian From: karim benhamouche [mailto:karim.benhamouche@ovnetworks.com] Sent: 16 January 2013 19:05 To: adrian@olddog.co.uk Cc: routing-discussion@ietf.org Subject: Re: FW: WG Review: Interface to the Routing System (i2rs) Hi Adrian, Is it related to SDN ? On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel wrote: FYI > -----Original Message----- > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] On Behalf Of The IESG > Sent: 15 January 2013 16:43 > To: IETF-Announce > Subject: WG Review: Interface to the Routing System (i2rs) > > A new IETF working group has been proposed in the Routing Area. The IESG > has not made any determination yet. The following draft charter was > submitted, and is provided for informational purposes only. Please send > your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22. > > Interface to the Routing System (i2rs) > ------------------------------------------------ ------=_NextPart_000_01E6_01CDF42A.34C2AE30 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = Karim,

 

What can I say? = RTFM.

 

Well, read the draft charter, = and read the I-Ds that exist. You can find the I-Ds by searching for = "-irs-" in the datatracker.

 

Also read the slides from the = BoF in Atlanta.

 

Cheers,

Adrian

 

From: karim benhamouche = [mailto:karim.benhamouche@ovnetworks.com]
Sent: 16 January = 2013 19:05
To: adrian@olddog.co.uk
Cc: = routing-discussion@ietf.org
Subject: Re: FW: WG Review: = Interface to the Routing System = (i2rs)

 

Hi = Adrian,

 

Is it related to SDN ?

 

On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel <adrian@olddog.co.uk> = wrote:

FYI

> = -----Original Message-----
> From: ietf-announce-bounces@ietf= .org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The = IESG
> Sent: 15 January 2013 16:43
> To: = IETF-Announce
> Subject: WG Review: Interface to the Routing = System (i2rs)
>
> A new IETF working group has been proposed = in the Routing Area. The IESG
> has not made any determination = yet. The following draft charter was
> submitted, and is provided = for informational purposes only. Please send
> your comments to = the IESG mailing list (iesg at ietf.org) by 2013-01-22.
>
> Interface = to the Routing System (i2rs)
> = ------------------------------------------------

------=_NextPart_000_01E6_01CDF42A.34C2AE30-- From karim.benhamouche@ovnetworks.com Wed Jan 16 12:55:24 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0820E11E80E6 for ; Wed, 16 Jan 2013 12:55:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuSKp9GuK8MC for ; Wed, 16 Jan 2013 12:55:23 -0800 (PST) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 4926411E80D2 for ; Wed, 16 Jan 2013 12:55:23 -0800 (PST) Received: by mail-ie0-f170.google.com with SMTP id k10so3454509iea.1 for ; Wed, 16 Jan 2013 12:55:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=R7Gq5PwQi2j4SCUSxE/v5a/vC6GTtmFaJEXqjfWBh5c=; b=nJ5Rf68HdSa0pLiy3teOR9nQrbwGuNA1dIPMD2/io9KUWs/1P/W0r3nGeUvnu7MSgb YxfmrG/Zbql5luJBfrztfhku8k1a+ZxZ5imhvxGk2p2BKDzkgKWKXyaDUB1RhM1uy8ib rTD3u2jSsGVKJDQWwxYtZRFq6hxqbASYt77BmKlygpYpCUjPKQLt5l5YPGv/GbDE1Mmm bfk7cvyESYUTTjn1g9/sr0ZH69KTMaD8WwRO6xVpaTrGTKDy9l/d5e3f2X/XLT20dLN9 SLT3doeLXQtDYF9RNxBg9KJdhie9FfYAODeqhZrech2TLP+MwVm3/6RvseKQtwI6ii0V l+OQ== MIME-Version: 1.0 X-Received: by 10.43.124.130 with SMTP id go2mr1614902icc.8.1358369722756; Wed, 16 Jan 2013 12:55:22 -0800 (PST) Received: by 10.64.12.129 with HTTP; Wed, 16 Jan 2013 12:55:22 -0800 (PST) X-Originating-IP: [184.144.110.53] In-Reply-To: <01e501cdf42a$34bdf340$9e39d9c0$@olddog.co.uk> References: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> <01e501cdf42a$34bdf340$9e39d9c0$@olddog.co.uk> Date: Wed, 16 Jan 2013 15:55:22 -0500 Message-ID: Subject: Re: FW: WG Review: Interface to the Routing System (i2rs) From: karim benhamouche To: adrian@olddog.co.uk Content-Type: multipart/alternative; boundary=bcaec517c690cc6d4b04d36e1845 X-Gm-Message-State: ALoCoQn8HxUhapJqAR4om7FI0U75QQaCR5em0+qapyuXr7AW1iZRxXcXfquZq/a8HYF/JTFPpgdC Cc: routing-discussion@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 20:55:24 -0000 --bcaec517c690cc6d4b04d36e1845 Content-Type: text/plain; charset=ISO-8859-1 I will do. Thanks for these informations. On Wed, Jan 16, 2013 at 3:43 PM, Adrian Farrel wrote: > Hi Karim,**** > > ** ** > > What can I say? RTFM.**** > > ** ** > > Well, read the draft charter, and read the I-Ds that exist. You can find > the I-Ds by searching for "-irs-" in the datatracker.**** > > ** ** > > Also read the slides from the BoF in Atlanta.**** > > ** ** > > Cheers,**** > > Adrian**** > > ** ** > > *From:* karim benhamouche [mailto:karim.benhamouche@ovnetworks.com] > *Sent:* 16 January 2013 19:05 > *To:* adrian@olddog.co.uk > *Cc:* routing-discussion@ietf.org > *Subject:* Re: FW: WG Review: Interface to the Routing System (i2rs)**** > > ** ** > > Hi Adrian,**** > > ** ** > > Is it related to SDN ?**** > > ** ** > > On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel > wrote:**** > > FYI > > > -----Original Message----- > > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > > bounces@ietf.org] On Behalf Of The IESG > > Sent: 15 January 2013 16:43 > > To: IETF-Announce > > Subject: WG Review: Interface to the Routing System (i2rs) > > > > A new IETF working group has been proposed in the Routing Area. The IESG > > has not made any determination yet. The following draft charter was > > submitted, and is provided for informational purposes only. Please send > > your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22. > > > > Interface to the Routing System (i2rs) > > ------------------------------------------------**** > --bcaec517c690cc6d4b04d36e1845 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I will do.
Thank= s for these informations.


On Wed, Jan 16, 2013 at 3:43 PM, Adrian = Farrel <adrian@olddog.co.uk> wrote:

Hi Karim,

=A0<= /p>

What can I say? RTFM.<= u>

=A0<= /p>

Well, read the draft c= harter, and read the I-Ds that exist. You can find the I-Ds by searching fo= r "-irs-" in the datatracker.

=A0<= /p>

Also read the slides f= rom the BoF in Atlanta.

=A0<= /p>

Cheers,<= /span>

Adrian

=A0

From: karim benhamouche [mailto:= karim= .benhamouche@ovnetworks.com]

Sent: 16 January 2013 19:05
To: adrian@olddog.c= o.uk
Cc: routing-discussion@ietf.org
Subject: Re: FW: WG Review: Interface to the Routing System (i= 2rs)

=A0

Hi Adrian,

=A0

Is it related to SDN ?

=A0

On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:=

FYI

> -----Origina= l Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org= ] On Behalf Of The IESG
> Sent: 15 January 2013 16:43
> To:= IETF-Announce
> Subject: WG Review: Interface to the Routing System = (i2rs)
>
> A new IETF working group has been proposed in the Routing Area= . The IESG
> has not made any determination yet. The following draft = charter was
> submitted, and is provided for informational purposes o= nly. Please send
> your comments to the IESG mailing list (iesg at ietf.org) by 2013-01-22.
>
> Interf= ace to the Routing System (i2rs)
> ----------------------------------= --------------


--bcaec517c690cc6d4b04d36e1845-- From abdussalambaryun@gmail.com Thu Jan 17 15:32:17 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF3721F8A22 for ; Thu, 17 Jan 2013 15:32:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.584 X-Spam-Level: X-Spam-Status: No, score=-3.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kB+PpiJVIoeP for ; Thu, 17 Jan 2013 15:32:15 -0800 (PST) Received: from mail-vb0-f42.google.com (mail-vb0-f42.google.com [209.85.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id B00BE21F8A03 for ; Thu, 17 Jan 2013 15:32:15 -0800 (PST) Received: by mail-vb0-f42.google.com with SMTP id ff1so718647vbb.1 for ; Thu, 17 Jan 2013 15:32:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=vbNui6AlT4HBa0SUIebHiqDJpEhrmw1oDwkOvLLJVB4=; b=L8bkE36b1hFmqZO0cvw0G+dqYP16UZ67ifVgdlqlDO5Y0z+/0JOagRFSC3CsJQ72qb gOdiVtmaIk5vcyS8AjPiauJ7qK8MzWqxFxD5bGCNMuO00thGcQRc8gxmxcq+epyEyNBK USmYUJ4VDJfxvst/W/0VLuyIZTKtaCkZ5u1JbBaD2Sn/0vd907j2qqulhLPuFIFbEu4p UnwNzLJJi4sFXTDEYhM0Gn23o0N33Zqu/Zna+f1L+hUxoTJQQMN45AnLSF8dCOoY2koN 71aBJ/K3Ao79s0SvDngtzt/KasxTWDfsOKCZ52L4Bw4se0uRetXg93mkRm2xbsVti03x nDDA== MIME-Version: 1.0 X-Received: by 10.52.23.238 with SMTP id p14mr6587585vdf.86.1358465535080; Thu, 17 Jan 2013 15:32:15 -0800 (PST) Received: by 10.220.145.5 with HTTP; Thu, 17 Jan 2013 15:32:14 -0800 (PST) In-Reply-To: References: <20130115164317.19158.38315.idtracker@ietfa.amsl.com> <00ab01cdf405$9d332140$d79963c0$@olddog.co.uk> Date: Fri, 18 Jan 2013 00:32:14 +0100 Message-ID: Subject: Re: FW: WG Review: Interface to the Routing System (i2rs) From: Abdussalam Baryun To: karim benhamouche Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: routing-discussion@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 23:32:17 -0000 Hi Karim, I don't think it is related only if this SDN ir related-to/includes routing systems, but I think we will start to discuss if related or not. AB On 1/16/13, karim benhamouche wrote: > Hi Adrian, > > Is it related to SDN ? > > > > ------------------------------------------------------ > *Karim Benhamouche, CCIE #24645 > * > Sr. IP Network Specialist and CEO > Sp=E9cialiste S=E9nior en R=E9seaux IP et Pr=E9sident > Montreal: (514) 371-0734 / Toronto: (647) 874-5544 > Email / Courriel: karim.benhamouche@ovnetworks.com > > > On Wed, Jan 16, 2013 at 11:21 AM, Adrian Farrel > wrote: > >> FYI >> >> > -----Original Message----- >> > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- >> > bounces@ietf.org] On Behalf Of The IESG >> > Sent: 15 January 2013 16:43 >> > To: IETF-Announce >> > Subject: WG Review: Interface to the Routing System (i2rs) >> > >> > A new IETF working group has been proposed in the Routing Area. The >> > IESG >> > has not made any determination yet. The following draft charter was >> > submitted, and is provided for informational purposes only. Please sen= d >> > your comments to the IESG mailing list (iesg at ietf.org) by >> > 2013-01-22. >> > >> > Interface to the Routing System (i2rs) >> > ------------------------------------------------ >> > Current Status: Proposed Working Group >> > >> > Assigned Area Director: >> > Adrian Farrel >> > >> > Mailing list >> > Address: i2rs@ietf.org >> > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs >> > Archive: >> > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html >> > >> > Charter of Working Group: >> > >> > Working Group Name: >> > Interfaces to the Routing System (I2RS) >> > >> > IETF Area: >> > Routing Area >> > >> > Chair(s): >> > TBD >> > Routing Area Director(s): >> > Adrian Farrel >> > Routing Area Advisor: >> > Adrian Farrel >> > Operations Area Advisor: >> > TBD >> > >> > Mailing Lists: >> > General Discussion: i2rs@ietf.org >> > To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs >> > Archive: >> > http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html >> > >> > Description of Working Group: >> > >> > In an IP routed network, the routing system: >> > >> > - Distributes topology and other state (network metadata) >> > - Uses this network metadata to determine the best path to each given >> > reachable destination attached to the network >> > - Communicates these decisions to the forwarding plane of each >> > forwarding device in the network. >> > >> > That is, the routing system is the collection of entities, protocols >> > and processes that collectively build the forwarding tables that are >> > exported into the entities that constitute the network's fowarding >> > plane. >> > >> > While processes participating in the routing system are often >> > colocated >> > with the local forwarding elements, this isn't a necessary condition. >> > Thus, the routing system includes control plane protocols that comput= e >> > routes and paths for data packets, wherever the processes implementin= g >> > those protocols may be running. >> > >> > I2RS facilitates real-time or event driven interaction with the >> > routing >> > system through a collection of protocol-based control or management >> > interfaces. These allow information, policies, and operational >> > parameters to be injected into and retrieved (as read or by >> > notification) from the routing system while retaining data consistenc= y >> > and coherency across the routers and routing infrastructure, and amon= g >> > multiple interactions with the routing system. The I2RS interfaces >> > will >> > co-exist with existing configuration and management systems and >> > interfaces. >> > >> > It is envisioned that users of the I2RS interfaces will be management >> > applications, network controllers, and user applications that make >> > specific demands on the network. >> > >> > The I2RS working group works to develop a high-level framework and >> > architecture that describes the basic building-blocks necessary to >> > enable the specific use cases, and that will lead to an understanding >> > of the abstract informational models and requirements for >> > encodings and protocols for the I2RS interfaces. Small and well-scope= d >> > use cases are critical to constrain the scope of the work and achieve >> > sufficient focus for the working group to deliver successful outcomes= . >> > Initial work within the working group will be limited to a single >> > administrative domain. >> > >> > The working group is chartered to work on the following items: >> > >> > - High-level architecture and framework for I2RS including >> > considerations of policy and security. >> > >> > - Tightly scoped key use cases for operational use of I2RS as follows= : >> > o Interactions with the Routing Information Base (RIB). Allowing >> > read and write access to the RIB, but no direct access to the >> > Forwarding Information Base (FIB). >> > o Control and analysis of the operation of the Border gateway >> > Protocol (BGP) including the setting and activation of policies >> > related to the protocol. >> > o Control, optimization, and choice of traffic exit points from >> > networks based on more information than provided by the dynamic >> > control plane. >> > o Distributed reaction to network-based attacks through quickly >> > modification of the control plane behavior to reroute traffic fo= r >> > one destination while leaving a standard mechanisms (filters, >> > metrics, and policy) in place for other routes. >> > o Service layer routing to improve on existing hub-and-spoke >> > traffic. >> > o The ability to extract information about topology from the >> > network. Injection and creation of topology will not be >> > considered >> > as an initial work item. >> > >> > Other use cases may be adopted by the working group only through >> > rechartering. >> > >> > - Abstract information models consistent with the use cases. >> > >> > - Requirements for I2RS protocols and encoding languages. >> > >> > - An analysis of existing IETF and other protocols and encoding >> > languages against the requirements. >> > >> > The working group is not currently chartered to develop protocols, >> > encoding languages, or data models. The objective of this work effort >> > is to arrive at common standards for these items, but these items are >> > dependent on the progress of the topics listed above. Work for these >> > items will be conducted in this working group only after a re-charter= , >> > and/or may be carried out in another working group with specific >> > responsibility for the protocol or encoding language. >> > >> > Goals and Milestones: >> > >> > Jul 2013: Request publication of an Informational document defining th= e >> > problem statement >> > Jul 2013: Request publication of an Informational document defining th= e >> > highlevel architecture and framework >> > Aug 2013: Request publication of Informational documents describing us= e >> > cases >> > Sep 2013: Request publication of an Informational document defining th= e >> > protocol requirements >> > Sep 2013: Request publication of an Informational document defining >> > encoding language requirements >> > Nov 2013: Request publication of Standards Track documents specifying >> > information models >> > Nov 2013: Request publication of an Informational document providing a= n >> > analysis of existing IETF and other protocols and encoding >> > languages against the requirements >> > Dec 2013: Consider re-chartering >> > >> >> >> _______________________________________________ >> routing-discussion mailing list >> routing-discussion@ietf.org >> https://www.ietf.org/mailman/listinfo/routing-discussion >> > From adrian@olddog.co.uk Wed Jan 23 10:21:59 2013 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4CB21F84E6 for ; Wed, 23 Jan 2013 10:21:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.568 X-Spam-Level: X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuQcrZXXLuyo for ; Wed, 23 Jan 2013 10:21:53 -0800 (PST) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 39EDC21F8A5E for ; Wed, 23 Jan 2013 10:21:51 -0800 (PST) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0NILnom014613 for ; Wed, 23 Jan 2013 18:21:49 GMT Received: from 950129200 (089144192006.atnat0001.highway.a1.net [89.144.192.6]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0NILlNE014548 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 23 Jan 2013 18:21:48 GMT From: "Adrian Farrel" To: Subject: FW: Call for Comment: 'Privacy Considerations for Internet Protocols' Date: Wed, 23 Jan 2013 18:21:47 -0000 Message-ID: <015801cdf996$826992e0$873cb8a0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0159_01CDF996.826BDCD0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac35jlpoICVTo8ppSxqLcG1BEAhagg== Content-language: en-gb X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 18:21:59 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0159_01CDF996.826BDCD0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =20 Privacy issues may have somewhat less impact on the Routing Area than = they do on other IETF areas. However, this document is still worth your = time and consideration. =20 Please note the details in the mail below about how to provide feedback. = Discussion of this document on *this* mailing list should be limited to = topics related to routing, and you should not assume that the IAB is = monitoring this mailing list. =20 Cheers, Adrian =20 From: ietf-announce-bounces@ietf.org = [mailto:ietf-announce-bounces@ietf.org] On Behalf Of IAB Chair Sent: 16 January 2013 22:31 To: ietf-announce@ietf.org Subject: Call for Comment: 'Privacy Considerations for Internet = Protocols' =20 This is an announcement of an IETF-wide Call for Comment on 'Privacy = Considerations for Internet Protocols'.=20 =20 The document is being considered for publication as an Informational RFC = within the IAB stream, and is available for inspection here:=20 http://tools.ietf.org/html/draft-iab-privacy-considerations =20 The Call for Comment will last until February 18, 2013. Please send = comments to iab at iab.org or submit them via TRAC = (see below).=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 Submitting Comments via TRAC=20 1. To submit an issue in TRAC, you first need to login to the IAB site = on the tools server:=20 http://tools.ietf.org/wg/iab/trac/login=20 =20 2. If you don't already have a login ID, you can obtain one by = navigating to this site:=20 http://trac.tools.ietf.org/newlogin=20 =20 3. Once you have obtained an account, and have logged in, you can file = an issue by navigating to the ticket entry form:=20 http://trac.tools.ietf.org/wg/iab/trac/newticket=20 =20 4. When opening an issue:=20 a. The Type: field should be set to "defect" for an issue with the = current document text, or "enhancement" for a proposed addition of = functionality (such as an additional requirement).=20 b. The Priority: field is set based on the severity of the Issue. For = example, editorial issues are typically "minor" or "trivial".=20 c. The Milestone: field should be set to milestone1 (useless, I know).=20 d. The Component: field should be set to the document you are filing the = issue on.=20 e. The Version: field should be set to "1.0".=20 f. The Severity: field should be set to based on the status of the = document (e.g. "In WG Last Call" for a document in IAB last call)=20 g. The Keywords: and CC: fields can be left blank unless inspiration = seizes you.=20 h. The Assign To: field is generally filled in with the email address of = the editor.=20 =20 5. Typically it won't be necessary to enclose a file with the ticket, = but if you need to, select "I have files to attach to this ticket".=20 =20 6. If you want to preview your Issue, click on the "Preview" button. = When you're ready to submit the issue, click on the "Create Ticket" = button.=20 =20 7. If you want to update an issue, go to the "View Tickets" page:=20 http://trac.tools.ietf.org/wg/iab/trac/report/1=20 =20 Click on the ticket # you want to update, and then modify the ticket = fields as required.=20 ------=_NextPart_000_0159_01CDF996.826BDCD0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi,

 

Privacy issues may have somewhat less impact on the Routing Area than = they do on other IETF areas. However, this document is still worth your = time and consideration.

 

Please note the details in the mail below about how to provide = feedback. Discussion of this document on *this* mailing list should be = limited to topics related to routing, and you should not assume that the = IAB is monitoring this mailing list.

 

Cheers,

Adrian

 

From: = ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] = On Behalf Of IAB Chair
Sent: 16 January 2013 = 22:31
To: ietf-announce@ietf.org
Subject: Call for = Comment: 'Privacy Considerations for Internet = Protocols'

 

This is an = announcement of an IETF-wide Call for Comment on 'Privacy Considerations = for Internet Protocols'. 
 
The document is being = considered for publication as an Informational RFC within the IAB = stream, and is available for inspection = here: 

 
The Call = for Comment will last until February 18, 2013. Please send = comments to iab at iab.org or = submit them via TRAC (see = below). 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 
Submit= ting Comments via TRAC 
1. To submit an issue in TRAC, you first = need to login to the IAB site on the tools server: 
http://tools.ietf.org/wg= /iab/trac/login 
 
2. If you don't already have a = login ID, you can obtain one by navigating to this site: 
http://trac.tools.ietf.org/n= ewlogin 
 
3. Once you have obtained an account, and = have logged in, you can file an issue by navigating to the ticket entry = form: 
http://trac.too= ls.ietf.org/wg/iab/trac/newticket 
 
4. When opening = an issue: 
a. The Type: field should be set to = "defect" for an issue with the current document text, or = "enhancement" for a proposed addition of functionality (such = as an additional requirement). 
b. The Priority: field is = set based on the severity of the Issue. For example, editorial issues = are typically "minor" or "trivial". 
c. The = Milestone: field should be set to milestone1 (useless, I = know). 
d. The Component: field should be set to the document = you are filing the issue on. 
e. The Version: field should be = set to "1.0". 
f. The Severity: field should be set to = based on the status of the document (e.g. "In WG Last Call" = for a document in IAB last call) 
g. The Keywords: and CC: = fields can be left blank unless inspiration seizes you. 
h. The = Assign To: field is generally filled in with the email address of the = editor. 
 
5. Typically it won't be necessary to enclose = a file with the ticket, but if you need to, select "I have files to = attach to this ticket". 
 
6. If you want to = preview your Issue, click on the "Preview" button. When you're = ready to submit the issue, click on the "Create Ticket" = button. 
 
7. If you want to update an issue, go to the = "View Tickets" page: 
http://trac.tool= s.ietf.org/wg/iab/trac/report/1 
 
Click on the = ticket # you want to update, and then modify the ticket fields as = required. 

------=_NextPart_000_0159_01CDF996.826BDCD0--