
From nobody Mon Aug  1 17:03:28 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E6112D0E4; Mon,  1 Aug 2016 17:03:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-bgp-pic-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802000327.2939.78291.idtracker@ietfa.amsl.com>
Date: Mon, 01 Aug 2016 17:03:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/1YGShH-uGxS9MggYW-LAiH3jGa4>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 00:03:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : Abstract
        Authors         : Ahmed Bashandy
                          Clarence Filsfils
                          Prodosh Mohapatra
	Filename        : draft-ietf-rtgwg-bgp-pic-02.txt
	Pages           : 25
	Date            : 2016-08-01

Abstract:
In the network comprising thousands of iBGP peers exchanging millions
of routes, many routes are reachable via more than one next-hop.
Given the large scaling targets, it is desirable to restore traffic
after failure in a time period that does not depend on the number of
BGP prefixes. In this document we proposed an architecture by which
traffic can be re-routed to ECMP or pre-calculated backup paths in a
timeframe that does not depend on the number of BGP prefixes. The
objective is achieved through organizing the forwarding data
structures in a hierarchical manner and sharing forwarding elements
among the maximum possible number of routes. The proposed technique
achieves prefix independent convergence while ensuring incremental
deployment, complete automation, and zero management and provisioning
effort. It is noteworthy to mention that the benefits of BGP-PIC are
hinged on the existence of more than one path whether as ECMP or
primary-backup.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-pic/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-pic-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-bgp-pic-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Aug  1 17:09:30 2016
Return-Path: <bashandy@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECBA12B05D; Mon,  1 Aug 2016 17:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.797
X-Spam-Level: 
X-Spam-Status: No, score=-15.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 EWAyCDMBVYIC; Mon,  1 Aug 2016 17:09:24 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E775112D0A3; Mon,  1 Aug 2016 17:09:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=74372; q=dns/txt; s=iport; t=1470096564; x=1471306164; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=IpmmwPRd7TsEjG1tpjFHvsiADild0CvMQeSTGBGLFZk=; b=fqPUySvrzFutXAILs6qnQESF+KXO29EAVaYDGN6NANt6knXy0gkpZdwC QapIAcWwApH2NA4bQtkPzEV9kbZeo7m1BSTeUetMI/dWLPcp9xaavg0vV L+WBZcxHm2LiNDBaMQXzpRgmvYt4tgbHcsevdk+2p6bBsU3aWOyYxeXU5 Y=;
X-IronPort-AV: E=Sophos;i="5.28,457,1464652800";  d="scan'208,217";a="305377719"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Aug 2016 00:09:23 +0000
Received: from [128.107.147.27] (dhcp-128-107-147-27.cisco.com [128.107.147.27]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u7209M71015844; Tue, 2 Aug 2016 00:09:22 GMT
Message-ID: <579FE4B2.3060607@cisco.com>
Date: Mon, 01 Aug 2016 17:09:22 -0700
From: "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: bruno.decraene@orange.com
Subject: Re: RtgDir review: draft-ietf-rtgwg-bgp-pic-00
References: <18205_1461160419_571789E3_18205_2694_2_53C29892C857584299CBF5D05346208A0F8761E1@OPEXCLILM21.corporate.adroot.infra.ftgroup> <57696CFD.8080907@cisco.com> <17434_1469694891_5799C3AB_17434_7712_1_53C29892C857584299CBF5D05346208A0F96B4C2@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <17434_1469694891_5799C3AB_17434_7712_1_53C29892C857584299CBF5D05346208A0F96B4C2@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------020502000109090102010808"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/3LTVTybmxtnzbWccTlehhdJPZ9g>
Cc: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "draft-ietf-rtgwg-bgp-pic.all@ietf.org" <draft-ietf-rtgwg-bgp-pic.all@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 00:09:28 -0000

This is a multi-part message in MIME format.
--------------020502000109090102010808
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Thanks a lot for the detailed review. I have uploaded version 02 
containing corrections for the typos indicated.

I am also CCing Jeff and Rob (the shepherd)

Ahmed

On 7/28/2016 1:34 AM, bruno.decraene@orange.com wrote:
> Re: RtgDir review: draft-ietf-rtgwg-bgp-pic-00
>
> Hi Ahmed,
>
> Many thanks for the updated version and your below answers.
>
> Looks good to me.
>
> Please find below 2 minor typos
>
> Thanks.
>
> Bruno
>
> :s/unreacreachable/unreachable
>
> :s/hierarchal/hierarchical
>
> *From:*rtgwg [mailto:rtgwg-bounces@ietf.org] *On Behalf Of *Ahmed 
> Bashandy (bashandy)
> *Sent:* Tuesday, June 21, 2016 6:36 PM
> *To:* rtg-ads@ietf.org
> *Cc:* draft-ietf-rtgwg-bgp-pic.all@ietf.org; rtgwg@ietf.org
> *Subject:* Re: RtgDir review: draft-ietf-rtgwg-bgp-pic-00
>
> Hi,
>
> Thanks a lot for the detailed review.
>
> I submitted version 01.  I CCed Jeff and Rob Shakir, who volunteered 
> to be a shepherd (Thanks a lot):):)
>
> I have restructured the document to address your comment. Besides I 
> went over all the "Minor issues" as well as "nits" and corrected them, 
> except 1-2 comments which I explained why I did not make the 
> modifications.
>
> Version 01 is modified and now it contains an "overview" section. 
> Hence all sections have been shifted by one. So for example, the 
> comment about section 2.3.3 now applies to section 3.2
>
> Please see my reply inline  starting with "#Ahmed"
>
> Thanks
>
> Ahmed
>
> On 4/20/2016 6:53 AM, bruno.decraene@orange.com 
> <mailto:bruno.decraene@orange.com> wrote:
>
>     Hello,
>
>     I have been selected as the Routing Directorate reviewer for this
>     draft. The Routing Directorate seeks to review all routing or
>     routing-related drafts as they pass through IETF last call and
>     IESG review, and sometimes on special request. The purpose of the
>     review is to provide assistance to the Routing ADs. For more
>     information about the Routing Directorate, please see ​
>     http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>
>     Although these comments are primarily for the use of the Routing
>     ADs, it would be helpful if you could consider them along with any
>     other IETF Last Call comments that you receive, and strive to
>     resolve them through discussion or by updating the draft.
>
>     Document: draft-ietf-rtgwg-bgp-pic-00
>     Reviewer: Bruno Decraene
>     IETF LC End Date: “QA review” pre WG LC
>     Intended Status: Informational
>
>     *Summary:*
>
>     I have some minor concerns about this document that I think should
>     be resolved before publication.
>
>     *Comments:*
>
>     - Document is interesting. Document is relatively clear but
>     sometime it feels like there is a little room for some
>     reformulation/edition to improve fluidity. In particular, the
>     learning curve is a bit steep at the beginning of the doc as most
>     of the concepts are introduced in 3 pages (pages 4-6) in the form
>     of a list of terminology and a pseudo code. I would find useful to
>     have an overview section just after the introduction, with a high
>     level view of the solution with a limited number of new terms.
>
>     - The text feels like authoritative, while probably many terms are
>     implementation specific. A priori, I would not expect all
>     implementation of BGP PIC to use the same terms, and possibly not
>     the same data structure. May be the text could be generalized to
>     cover multiple implementations; or modified to describe a
>     generalized concept (i.e. data-structure designed to share as much
>     data as possible between elements, at the cost of additional
>     indirections); or the document could state that it describes a
>     specific implementation with implementations specific terminology,
>     data structure, and specifics. Or a combination of both (e.g.
>     adding a section being both generalized and describing the
>     concept, and then the existing sections after stating that they
>     are specific to one implementation).
>
> #Ahmed: I have restructured the document to make much more general. 
> Please take a look. All feedback is most welcomed.
>
> *Minor Issues:*
>
> - I find figure 2 very useful to understand the data-structure. I 
> would move it sooner in the doc, somewhere before §2.2. (with its 
> subsequent text below) e.g. a new §2.2 "FIB data-structure"
>
> It would need to be generalized i.e. example non-specific. I could 
> think of:
>
> IP Leaf: Pathlist:       IP Leaf:                Pathlist:
>
> -------- ---------       -------                 --------
>
> BGP NLRI ---> BGP NH1   ----> IGP IP1 (BGP NH1)  ---> IGP NH1, I1 ---> 
> Adjacency1
>
> BGP NHi --...                         IGP NHi, Ii  --..
>
> |                                    |
>
> |                                         |
>
> |                                         |
>
> v                                         v
>
> OutLabel Array:                           OutLabel Array:
>
> --------------                            --------------
>
>           L (NLRI, NH1)                             L (IP1, NH1)
>
> L (NLRI, NHi)                             L (IP1, NHi)
>
> - Figure 1 could be enhanced with IGP-NH1, IGP-NH2, I1 and I2.
>
> #Ahmed: Corrected
>
>
> - Example 3 does not use the same naming convention than examples 1 
> and 2, this make it harder to follow for a priori no reason. e.g. VPN 
> labels are named VPN-L11 in examples 1 and 2, but are named 
> VPN-PE21(P1) in exmaple 3; transport labels are named LDP-L12 in 
> exmaples 1 and 2, but LASBR11(PE22) and L11 in figure 3.
>
> #Ahmed: I renamed the VPN labels to conform to the convention used in 
> Examples 1 and 2. Also All IGP labels were renamed to IGP-Lij to make 
> them applicable to both LDP and Segment routing.
> For ASBR labels, we need to differentiate between ASBR labels and IGP 
> labels. Hence the labels advertised by ASBRs are named differently.
>
>
> - §2.3.3
>
> "The local labels of the next hops".
>
>  - All labels are locally assigned. So what do you mean by "local"
>
> - "next-hop" sometimes refers to IGP/connected next-hop (a priori the 
> case here) and sometimes to BGP next-hop. I find it hard to follow. I 
> rather use a different name (e.g; connected next-hop vs BGP next-hop)
>
> #Ahmed: Corrected.
>
> - §3
>
> "the hashing at the BGP level yields path 0 while the hashing at the 
> IGP level yields path 1. In that case, the packet will be sent out of 
> interface I1 with the label stack "LDP-L12,VPN-L21".
>
> Does not seem to match my understanding. For "LDP-L12,VPN-L21" I would 
> assume BGP used path index 1 and IGP used path index 0.
>
> #Ahmed: Corrected.
>
> IMHO:
>
> OLD: "Hence ASBR22 swaps "LASBR22(PE22)" with the LDP/SR label of 
> PE22, pushes the label of the next-hop towards PE22 in domain 2, and 
> sends the packet along the shortest path towards PE22."
>
> NEW: "Hence ASBR22 swaps "LASBR22(PE22)" with the LDP/SR label for 
> PE22 advertised by the next-hop towards PE22 in domain 2, and sends 
> the packet along the shortest path towards PE22."
>
> (in all cases "swaps" then "pushes" would increase the label stack by 
> 1, which is not the case.)
>
> #Ahmed: Corrected
>
> §4.1
>
> "the useable paths in the loadinfo"
>
> loadinfo is a proprietary FIB datastructure which has not been 
> introduced/defined. You need to either remove that term (if possible) 
> or define it somewhere.
>
> #Ahmed: Corrected. "loadinfo" is replaced with "pathlist", which is 
> the intended term
>
> "Hence traffic restoration occurs within the time frame of IGP 
> convergence,"
>
> agree.
>
> ..."and, for local link failure, within the timeframe of local 
> detection. Thus it is possible to achieve sub-50 msec convergence as 
> described in [10] for local link failure"
>
> IMO, this is restricted to specific cases. e.g. external (eBGP) link 
> failure, ECMP case, possibly IP FRR.  So possibly
>
> OLD: for local link failure, within the timeframe of local detection. 
> Thus it is possible to achieve sub-50 msec convergence as described in 
> [10] for local link failure
>
> NEW: for local link failure, assuming a backup path has been 
> precomputed, within the timeframe of local detection (e.g. 50ms). 
> Example of solutions precomputing a backup path are IP FRR [LFA], 
> [RLFA], [MRT], [TI-LFA] or eBGP path having a backup path [10].
>
> #Ahmed: Corrected
>
> §4
>
> I would find useful to indicate, for each type of failure, the number 
> of data-structure that need to be updated.
>
> #Ahmed: In general it is not always possible to know the number of 
> updated data structures due to a topology change because it depends on 
> the topology itself. For example, in Section 5.1 (The section about 
> BGP-PIC core), it is not possible to outline the datastructures that 
> are modified for a remote link failure. However for local link 
> failure, we added a statement in second paragraph of Section 5.1 
> indicating that only pathlists with paths using the local link need to 
> be updated. We also indicated in the 3rd paragraph that datastructures 
> are modified starting from the IGP leaves without walking back to BGP 
> pathlists or data structures
>
> ---
>
> §4.2.2
>
> "To avoid loops, ePE2 MUST treat any core facing path as a backup
>
>       path, otherwise ePE2 may redirect traffic arriving from the core
>
>       back to ePE1 causing a loop."
>
> Looks a bit under-described to me. Could you please elaborate a bit? 
> In particular:
>
> - if 2 PE (PE1, PE2) are connected in U to 2 P (P1, P2)     
> (P1-PE1-PE2-P2), PE1 being nominal and PE2 only used in backup, in the 
> nominal situation, if the core network sends the trafic to PE1 via PE2 
> (used as a P/transit), how does PE2 know that it must send this 
> traffic to PE1? (rather than CE2)
>
> - this behavior looks like an additional specific feature. How doew 
> ePE1 knows that ePE2 have this feature?
>
> ---
>
> #Ahmed: The statement is removed. As mentioned in Section 6.1 how to 
> avoid loops in case of CE node failure is a different topic and needs 
> to be addressed separately
>
> §4.3
>
> "  Hence if the platform supports the "unflattened" forwarding chain,
>
>    then a single pathlist needs to be updated while if the platform
>
>    supports a shallower forwarding chain, then two pathlists need to be
>
>    updated."
>
> IINM "single"  and "two" pathlist applies to the specific example. In 
> this last sentence/summary, I'd prefer a more general statement. A 
> priori, without digging too much in this most complex use case, it 
> seems like :s/single/o(1) :s/two/o(PE) . The former looks close 
> (single vs o(1)) but IMHO there is a significant difference between 2 
> and o(PE) (i.e. 100s)
>
> #Ahmed: Agreed. The last paragraph is generalized and modified to 
> indicate possible outcomes of flattenning forwarding chains
>
> ---
>
> §5.1
>
> Good paragraph. It's quite clear that the convergence time does not 
> depend on the number of BGP prefixes, which is good. For the benefit 
> of the reader, it would be even more interesting if, for each type of 
> failure, the text could indicate on what it depends. e.g.  o(1), 
> o(connected interfaces), o(PE), o(PEnominal*PEbackup)....
>
> #Ahmed: Each subsection indicates the convergence time dependency. For 
> example, in Section 6.1.1, the last paragraph says that the dependence 
> is on the IGP convergence time only
>
> --
>
> §7
>
> "No additional security risk is introduced by using the mechanisms 
> proposed in this document"
>
> In general, with such a sentence, it's difficult to evaluate whether 
> the authors have very quickly evaluated the risk or if this evaluation 
> has been performed in details. So in general, some more text detailing 
> which aspects have been evaluated is interesting for the reader (yet 
> painful for the authors).
>
> As the document describe an internal box behavior, this is difficult 
> to evaluate and discuss. But from a bad experience, I fear that there 
> may be an impact. Indeed, with such structure, the FIB 
> structure/memory is typically different between BGP prefixes and IGP 
> prefixes. In general, the implementation is designed to support the 
> "right" numbers of both. But assuming an accident or an attack, the 
> numbers may not be "right". e.g. one upon a time, someone has 
> redistributed the BGP table into the IGP. In this case, the total 
> number of IP prefixes in the FIB is exactly the same. But as the data 
> structure used in the FIB was different between BGP and IGP prefixes, 
> the FIB ran out of memory and the line card crashed (well actually 
> only the IP FIB, so IS-IS hello packet were still correctly sent and 
> forwarded. As a result, traffic was permanently black holed)
>
> #Ahmed: I added a statement indicating that the behavior is internal 
> to the router.
> On another front, although the scenario that you mentioned is related 
> to reliability rather than security, it indicates that BGP-PIC 
> actually improves the reliability of FIB because it greatly reduces 
> the use of hardware and software memory
>
> ---
>
> § 9
>
> OLD: that allows achieving prefix independent convergence
>
> NEW: that allows achieving BGP prefixes independent convergence
>
> (it's still depend on the number of IGP prefixes and/or BGP pathlist)
>
> #Ahmed: Corrected
>
> *Nits:*
>
> Abstract
>
> "via more than one path."
>
> In this 1rst sentence, it's not clear what path really means. (e.g cf 
> the terminology section where you have more than one). I guess that 
> you mean "BGP path". (as there are also typically multiple IGP path to 
> reach each BGP Next Hop)
>
> #Ahmed: modified to next-hop to indicate BGP next-hops
>
> "The objective is achieved through organizing the forwarding chains"
>
> "chain" does not self self explicit to me. what about :s/chains/data 
> structure"
>
> #Ahmed: Agreed, changed to "data structures"
>
> "complete transparency"
>
> what do you mean? transparency to what / from who?
>
> #Ahmed: Removed the word "transparency
>
> §1
>
> OLD: to allow for more than one path for a given prefix
>
> NEW: to allow for BGP to advertise more than one path for a given prefix
>
> #Ahmed: Modified as suggested
>
> OLD: Another more common and widely deployed scenario is L3VPN with 
> multi-homed VPN sites
>
> NEW: Another more common and widely deployed scenario is L3VPN with 
> multi-homed VPN sites with unique Route Distinguisher.
>
> #Ahmed: Modified as suggested
>
> ---
>
> §1.2
>
> "Pathlist: It is an array of paths"
>
> "OutLabel-Array: The OutLabel-Array is a list of one or more outgoing 
> labels "
>
> So a list is defined as an array and the array is defined as a list :-).
>
> What about using the same term, e.g. a list?
>
> #Ahmed: Corrected. Both are now pathlist and OutLabel-List:)
>
> --
>
> The OutLabel-Array is a list of one or more
>
>       outgoing labels and/or label actions where each label or label
>
>       action has 1-to-1 correspondence to a path in the pathlist. It
>
>       is possible that the number of entries in the OutLabel-array is
>
>       different from the number of paths in the pathlist and the ith
>
>       Outlabel-Array entry is associated with the path whose path-
>
>       index is "i".
>
> - I don't see how one can have a 1-to-1 correspondance if the number 
> of elements is not the same.
>
> #Ahmed Corrected.
>
> - Last sentence could be splitted in 2.
>
> -- 
>
> Since the term ingres PE is defined, you could also detine the term 
> egress PE. Possibly in the same sentence.
>
> OLD: "Ingress PE, "iPE": It is a BGP speaker that learns about a
>
>       prefix through another IBGP peer and chooses that IBGP peer as
>
>       the next-hop for the prefix
>
> NEW:      "Ingress PE, "iPE": It is a BGP speaker that learns about a
>
>       prefix through a IBGP peer and chooses an egress PE as the 
> next-hop for the prefix.
>
> #Ahmed: Modified as suggested
>
> As a side note, the previous definition assume that there were no 
> Route Relfector (the iBGP peer is the BGP Next Hop)
>
> #Ahmed: Correct. I did not want to unnecessarily complicate the 
> discussion with information
>
> -- 
>
> §2.3
>
> Figure 1 represents a VPN network with 3 PE and a CE. In this context, 
> "VPN-P1" sounds a bit like a P router. What about :s/VPN-P1/VPN-IP1  ? 
> Same comment for IGP-P1.
>
> #Ahmed: Agreed. All modified as suggested
>
> --
>
> §2.3.2
>
> OLD: ePE2 constructs the forwarding chain depicted in Figure 1
>
> NEW: ePE2 constructs the forwarding chain depicted in Figure 3
>
> #Ahmed: Corrected
>
> OLD: VPL-L11
>
> NEW: VPN-L11
>
> #Ahmed: Corrected
>
> §2.3.3
>
> OLD: can reach ASBR1
>
> NEW: can reach ASBR11
>
> #Ahmed: Corrected
>
> OLD: The label for advertised by ASBR11 to iPE
>
> NEW: The label advertised by ASBR11 to iPE
>
> OLD: The labels for advertised by ASBR12 to iPE
>
> NEW: The labels advertised by ASBR12 to iPE
>
> #Ahmed: Corrected
>
> OLD: The labels for advertised to iPE by ASBR11 using BGP-LU
>
> NEW: The labels advertised  by ASBR11 to iPE using BGP-LU
>
> #Ahmed: Corrected
>
> ---
>
> §3
>
> OLD: Let's applying the above forwarding steps to the example 
> described in Figure 1 Section 2.3.1.
>
> OLD: Let's applying the above forwarding steps to the example 
> described in Figure 2 Section 2.3.1.
>
> #Ahmed: Corrected
>
> (somewhat guesssing. But in all cases, there is no figure 1 in section 
> 2.3.1)
>
> ---
>
> §4.1
>
> IMO
>
> OLD: As soon as the IGP convergence is effective for the BGP nhop 
> entry, the new forwarding state is immediately available to all 
> dependent BGP prefixes.
>
> NEW: As soon as the IGP convergence is effective for a BGP next-hop 
> entry, the new forwarding state is immediately available to all 
> dependent BGP prefixes.
>
> more generally
>
> :s/nhop/next-hop
>
> #Ahmed: Replaced nhop with next-hop in the entire document
>
> ---
>
> §4.3
>
> :s/PE222/PE22
>
> #Ahmed: Corrected
>
> Best regards,
>
> Bruno
>
> **
>
> _________________________________________________________________________________________________________________________
>   
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>   
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.


--------------020502000109090102010808
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thanks a lot for the detailed review. I have uploaded version 02
    containing corrections for the typos indicated.<br>
    <br>
    I am also CCing Jeff and Rob (the shepherd)<br>
    <br>
    Ahmed<br>
    <br>
    <div class="moz-cite-prefix">On 7/28/2016 1:34 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:17434_1469694891_5799C3AB_17434_7712_1_53C29892C857584299CBF5D05346208A0F96B4C2@OPEXCLILM21.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <title>Re: RtgDir review: draft-ietf-rtgwg-bgp-pic-00</title>
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"Préformaté HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New","serif";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.icon
	{mso-style-name:icon;}
span.PrformatHTMLCar
	{mso-style-name:"Préformaté HTML Car";
	mso-style-priority:99;
	mso-style-link:"Préformaté HTML";
	font-family:Consolas;
	color:black;
	mso-fareast-language:EN-US;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.insert
	{mso-style-name:insert;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Hi
            Ahmed,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Many
            thanks for the updated version and your below answers.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Looks
            good to me.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Please
            find below 2 minor typos<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Thanks.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Bruno<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">:s/</span><span
            class="insert">unreacreachable/unreachable<o:p></o:p></span></p>
        <p class="MsoNormal"><span class="insert">:s/hierarchal/hierarchical</span><span
            style="color:#1F497D" lang="EN-US"><o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext;mso-fareast-language:FR">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext;mso-fareast-language:FR">
                  rtgwg [<a class="moz-txt-link-freetext" href="mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>] <b>On Behalf Of
                  </b>Ahmed Bashandy (bashandy)<br>
                  <b>Sent:</b> Tuesday, June 21, 2016 6:36 PM<br>
                  <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rtg-ads@ietf.org">rtg-ads@ietf.org</a><br>
                  <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-rtgwg-bgp-pic.all@ietf.org">draft-ietf-rtgwg-bgp-pic.all@ietf.org</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
                  <b>Subject:</b> Re: RtgDir review:
                  draft-ietf-rtgwg-bgp-pic-00<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
            <br>
            Thanks a lot for the detailed review. <br>
            <br>
            I submitted version 01.  I CCed Jeff and Rob Shakir, who
            volunteered to be a shepherd (Thanks a lot):):)<br>
            <br>
            I have restructured the document to address your comment.
            Besides I went over all the "Minor issues" as well as "nits"
            and corrected them, except 1-2 comments which I explained
            why I did not make the modifications.<br>
            <br>
            Version 01 is modified and now it contains an "overview"
            section. Hence all sections have been shifted by one. So for
            example, the comment about section 2.3.3 now applies to
            section 3.2<br>
            <br>
            Please see my reply inline  starting with "#Ahmed"<br>
            <br>
            Thanks<br>
            <br>
            Ahmed<br>
            <br>
            <o:p></o:p></p>
          <div>
            <p class="MsoNormal">On 4/20/2016 6:53 AM, <a
                moz-do-not-send="true"
                href="mailto:bruno.decraene@orange.com">
                bruno.decraene@orange.com</a> wrote:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p><span lang="EN-US">Hello, </span><o:p></o:p></p>
            <p><span lang="EN-US">I have been selected as the Routing
                Directorate reviewer for this draft. The Routing
                Directorate seeks to review all routing or
                routing-related drafts as they pass through IETF last
                call and IESG review, and sometimes on special request.
                The purpose of the review is to provide assistance to
                the Routing ADs. For more information about the Routing
                Directorate, please see
              </span><a moz-do-not-send="true"
                href="http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir"><span
                  class="icon"><span lang="EN-US">​</span></span><span
                  lang="EN-US">http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir</span></a>
              <o:p></o:p></p>
            <p><span lang="EN-US">Although these comments are primarily
                for the use of the Routing ADs, it would be helpful if
                you could consider them along with any other IETF Last
                Call comments that you receive, and strive to resolve
                them through discussion or by updating the draft. </span><o:p></o:p></p>
            <p><span lang="EN-US">Document: draft-ietf-rtgwg-bgp-pic-00<br>
                Reviewer: Bruno Decraene <br>
                IETF LC End Date: “QA review” pre WG LC <br>
                Intended Status: Informational</span><o:p></o:p></p>
            <p><strong><span lang="EN-US">Summary:</span></strong><o:p></o:p></p>
            <p class="MsoNormal"><span lang="EN-US">I have some minor
                concerns about this document that I think should be
                resolved before publication.</span><o:p></o:p></p>
            <p><strong><span lang="EN-US">Comments:</span></strong><o:p></o:p></p>
            <p class="MsoNormal"><span lang="EN-US">- Document is
                interesting. Document is relatively clear but sometime
                it feels like there is a little room for some
                reformulation/edition to improve fluidity. In
                particular, the learning curve is a bit steep at the
                beginning of the doc as most of the concepts are
                introduced in 3 pages (pages 4-6) in the form of a list
                of terminology and a pseudo code. I would find useful to
                have an overview section just after the introduction,
                with a high level view of the solution with a limited
                number of new terms.</span><o:p></o:p></p>
            <p class="MsoNormal"><span lang="EN-US">- The text feels
                like authoritative, while probably many terms are
                implementation specific. A priori, I would not expect
                all implementation of BGP PIC to use the same terms, and
                possibly not the same data structure. May be the text
                could be generalized to cover multiple implementations;
                or modified to describe a generalized concept (i.e.
                data-structure designed to share as much data as
                possible between elements, at the cost of additional
                indirections); or the document could state that it
                describes a specific implementation with implementations
                specific terminology, data structure, and specifics. Or
                a combination of both (e.g. adding a section being both
                generalized and describing the concept, and then the
                existing sections after stating that they are specific
                to one implementation).</span><o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              I have restructured the document to make much more
              general. Please take a look. All feedback is most
              welcomed.<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><strong><span
                style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
                Issues:</span></strong><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- I find figure 2 very
              useful to understand the data-structure. I would move it
              sooner in the doc, somewhere before §2.2. (with its
              subsequent text below) e.g. a new §2.2 "FIB
              data-structure"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">It would need to be
              generalized i.e. example non-specific. I could think of:</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">IP Leaf:     
              Pathlist:       IP Leaf:                Pathlist:</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">--------     
              ---------       -------                 --------</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">BGP NLRI ---&gt;
              BGP NH1   ----&gt; IGP IP1 (BGP NH1)  ---&gt; IGP NH1, I1 
              ---&gt; Adjacency1</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">             
            </span><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;">BGP NHi  
              --...                         IGP NHi, Ii  --..</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;">               </span><span
              style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">|     
                                                 |</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">              
              |                                         |</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">               
              |                                         |</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">               
              v                                         v</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">         
              OutLabel Array:                           OutLabel Array:</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">         
              --------------                            --------------</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">          L
              (NLRI, NH1)                             L (IP1, NH1)</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;" lang="EN-US">         
            </span><span style="font-family:&quot;Courier
              New&quot;,&quot;serif&quot;">L (NLRI,
              NHi)                             L (IP1, NHi)</span><o:p></o:p></p>
          <p class="MsoNormal">                                              
              <o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- Figure 1 could be
              enhanced with IGP-NH1, IGP-NH2, I1 and I2.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">- Example 3 does not
              use the same naming convention than examples 1 and 2, this
              make it harder to follow for a priori no reason. e.g. VPN
              labels are named VPN-L11 in examples 1 and 2, but are
              named VPN-PE21(P1) in exmaple 3; transport labels are
              named LDP-L12 in exmaples 1 and 2, but LASBR11(PE22) and
              L11 in figure 3.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              I renamed the VPN labels to conform to the convention used
              in Examples 1 and 2. Also All IGP labels were renamed to
              IGP-Lij to make them applicable to both LDP and Segment
              routing. <br>
              For ASBR labels, we need to differentiate between ASBR
              labels and IGP labels. Hence the labels advertised by
              ASBRs are named differently.
              <br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">- §2.3.3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"The local labels of
              the next hops". </span>
            <o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> - All labels are
              locally assigned. So what do you mean by "local"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- "next-hop" sometimes
              refers to IGP/connected next-hop (a priori the case here)
              and sometimes to BGP next-hop. I find it hard to follow. I
              rather use a different name (e.g; connected next-hop vs
              BGP next-hop)</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected.
              <br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">- §3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"the hashing at the
              BGP level yields path 0 while the hashing at the IGP level
              yields path 1. In that case, the packet will be sent out
              of interface I1 with the label stack "LDP-L12,VPN-L21".</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Does not seem to match
              my understanding. For "LDP-L12,VPN-L21" I would assume BGP
              used path index 1 and IGP used path index 0.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected.<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">IMHO:</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: "Hence ASBR22
              swaps "LASBR22(PE22)" with the LDP/SR label of PE22,
              pushes the label of the next-hop towards PE22 in domain 2,
              and sends the packet along the shortest path towards
              PE22."
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: "Hence ASBR22
              swaps "LASBR22(PE22)" with the LDP/SR label for PE22
              advertised by the next-hop towards PE22 in domain 2, and
              sends the packet along the shortest path towards PE22."
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">(in all cases "swaps"
              then "pushes" would increase the label stack by 1, which
              is not the case.)</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§4.1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"the useable paths in
              the loadinfo"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">loadinfo is a
              proprietary FIB datastructure which has not been
              introduced/defined. You need to either remove that term
              (if possible) or define it somewhere.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected. "loadinfo" is replaced with "pathlist", which
              is the intended term<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"Hence traffic
              restoration occurs within the time frame of IGP
              convergence,"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">agree.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">..."and, for local
              link failure, within the timeframe of local detection.
              Thus it is possible to achieve sub-50 msec convergence as
              described in [10] for local link failure"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">IMO, this is
              restricted to specific cases. e.g. external (eBGP) link
              failure, ECMP case, possibly IP FRR.  So possibly</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: for local link
              failure, within the timeframe of local detection. Thus it
              is possible to achieve sub-50 msec convergence as
              described in [10] for local link failure</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: for local link
              failure, assuming a backup path has been precomputed,
              within the timeframe of local detection (e.g. 50ms).
              Example of solutions precomputing a backup path are IP FRR
              [LFA], [RLFA], [MRT], [TI-LFA] or eBGP path having a
              backup path [10]. </span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§4</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">I would find useful to
              indicate, for each type of failure, the number of
              data-structure that need to be updated.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              In general it is not always possible to know the number of
              updated data structures due to a topology change because
              it depends on the topology itself. For example, in Section
              5.1 (The section about BGP-PIC core), it is not possible
              to outline the datastructures that are modified for a
              remote link failure. However for local link failure, we
              added a statement in second paragraph of Section 5.1
              indicating that only pathlists with paths using the local
              link need to be updated. We also indicated in the 3rd
              paragraph that datastructures are modified starting from
              the IGP leaves without walking back to BGP pathlists or
              data structures<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§4.2.2</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"To avoid loops, ePE2
              MUST treat any core facing path as a backup</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      path, otherwise
              ePE2 may redirect traffic arriving from the core</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      back to ePE1
              causing a loop."</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">                  </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Looks a bit
              under-described to me. Could you please elaborate a bit?
              In particular:</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- if 2 PE (PE1, PE2)
              are connected in U to 2 P (P1, P2)     (P1-PE1-PE2-P2),
              PE1 being nominal and PE2 only used in backup, in the
              nominal situation, if the core network sends the trafic to
              PE1 via PE2 (used as a P/transit), how does PE2 know that
              it must send this traffic to PE1? (rather than CE2)</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- this behavior looks
              like an additional specific feature. How doew ePE1 knows
              that ePE2 have this feature?</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              The statement is removed. As mentioned in Section 6.1 how
              to avoid loops in case of CE node failure is a different
              topic and needs to be addressed separately<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">§4.3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"  Hence if the
              platform supports the "unflattened" forwarding chain,</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">   then a single
              pathlist needs to be updated while if the platform</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">   supports a
              shallower forwarding chain, then two pathlists need to be</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">   updated."</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">IINM "single"  and
              "two" pathlist applies to the specific example. In this
              last sentence/summary, I'd prefer a more general
              statement. A priori, without digging too much in this most
              complex use case, it seems like :s/single/o(1) 
              :s/two/o(PE) . The former looks close (single vs o(1)) but
              IMHO there is a significant difference between 2 and o(PE)
              (i.e. 100s)</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Agreed. The last paragraph is generalized and modified to
              indicate possible outcomes of flattenning forwarding
              chains<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§5.1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Good paragraph. It's
              quite clear that the convergence time does not depend on
              the number of BGP prefixes, which is good. For the benefit
              of the reader, it would be even more interesting if, for
              each type of failure, the text could indicate on what it
              depends. e.g.  o(1), o(connected interfaces), o(PE),
              o(PEnominal*PEbackup)....  
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Each subsection indicates the convergence time dependency.
              For example, in Section 6.1.1, the last paragraph says
              that the dependence is on the IGP convergence time only<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">--</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§7</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"No additional
              security risk is introduced by using the mechanisms
              proposed in this document"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">In general, with such
              a sentence, it's difficult to evaluate whether the authors
              have very quickly evaluated the risk or if this evaluation
              has been performed in details. So in general, some more
              text detailing which aspects have been evaluated is
              interesting for the reader (yet painful for the authors).</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">As the document
              describe an internal box behavior, this is difficult to
              evaluate and discuss. But from a bad experience, I fear
              that there may be an impact. Indeed, with such structure,
              the FIB structure/memory is typically different between
              BGP prefixes and IGP prefixes. In general, the
              implementation is designed to support the "right" numbers
              of both. But assuming an accident or an attack, the
              numbers may not be "right". e.g. one upon a time, someone
              has redistributed the BGP table into the IGP. In this
              case, the total number of IP prefixes in the FIB is
              exactly the same. But as the data structure used in the
              FIB was different between BGP and IGP prefixes, the FIB
              ran out of memory and the line card crashed (well actually
              only the IP FIB, so IS-IS hello packet were still
              correctly sent and forwarded. As a result, traffic was
              permanently black holed)</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              I added a statement indicating that the behavior is
              internal to the router.
              <br>
              On another front, although the scenario that you mentioned
              is related to reliability rather than security, it
              indicates that BGP-PIC actually improves the reliability
              of FIB because it greatly reduces the use of hardware and
              software memory<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§ 9</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: that allows
              achieving prefix independent convergence</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: that allows
              achieving BGP prefixes independent convergence
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">(it's still depend on
              the number of IGP prefixes and/or BGP pathlist)</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><strong><span
                style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits:</span></strong><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Abstract</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"via more than one
              path."</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">In this 1rst sentence,
              it's not clear what path really means. (e.g cf the
              terminology section where you have more than one). I guess
              that you mean "BGP path". (as there are also typically
              multiple IGP path to reach each BGP Next Hop)</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              modified to next-hop to indicate BGP next-hops<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"The objective is
              achieved through organizing the forwarding chains"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"chain" does not self
              self explicit to me. what about :s/chains/data structure"</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Agreed, changed to "data structures"<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"complete
              transparency"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">what do you mean?
              transparency to what / from who?</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Removed the word "transparency<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">§1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: to allow for more
              than one path for a given prefix
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: to allow for BGP
              to advertise more than one path for a given prefix</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Modified as suggested<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: Another more
              common and widely deployed scenario is L3VPN with
              multi-homed VPN sites</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: Another more
              common and widely deployed scenario is L3VPN with
              multi-homed VPN sites with unique Route Distinguisher.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Modified as suggested<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§1.2</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"Pathlist: It is an
              array of paths"</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">"OutLabel-Array: The
              OutLabel-Array is a list of one or more outgoing labels "</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">So a list is defined
              as an array and the array is defined as a list :-).</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">What about using the
              same term, e.g. a list?</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected. Both are now pathlist and OutLabel-List:)<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">--</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">The OutLabel-Array is
              a list of one or more</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      outgoing labels
              and/or label actions where each label or label</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      action has
              1-to-1 correspondence to a path in the pathlist. It</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      is possible that
              the number of entries in the OutLabel-array is</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      different from
              the number of paths in the pathlist and the ith</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      Outlabel-Array
              entry is associated with the path whose path-</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      index is "i".</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">                  </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">- I don't see how one
              can have a 1-to-1 correspondance if the number of elements
              is not the same.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed
              Corrected.<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">- Last sentence could
              be splitted in 2.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">--              </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Since the term ingres
              PE is defined, you could also detine the term egress PE.
              Possibly in the same sentence.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: "Ingress PE,
              "iPE": It is a BGP speaker that learns about a</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      prefix through
              another IBGP peer and chooses that IBGP peer as</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      the next-hop for
              the prefix</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">                  </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW:      "Ingress PE,
              "iPE": It is a BGP speaker that learns about a</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">      prefix through a
              IBGP peer and chooses an egress PE as the next-hop for the
              prefix.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Modified as suggested<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">                  </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">As a side note, the
              previous definition assume that there were no Route
              Relfector (the iBGP peer is the BGP Next Hop)        
            </span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Correct. I did not want to unnecessarily complicate the
              discussion with information<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">         </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">-- </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§2.3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Figure 1 represents a
              VPN network with 3 PE and a CE. In this context, "VPN-P1"
              sounds a bit like a P router. What about
              :s/VPN-P1/VPN-IP1  ? Same comment for IGP-P1.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Agreed. All modified as suggested<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">--</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§2.3.2</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: ePE2 constructs
              the forwarding chain depicted in Figure 1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: ePE2 constructs
              the forwarding chain depicted in Figure 3</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: VPL-L11</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: VPN-L11</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§2.3.3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: can reach ASBR1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: can reach ASBR11</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: The label for
              advertised by ASBR11 to iPE</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: The label
              advertised by ASBR11 to iPE</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: The labels for
              advertised by ASBR12 to iPE</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: The labels
              advertised by ASBR12 to iPE</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: The labels for
              advertised to iPE by ASBR11 using BGP-LU</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: The labels
              advertised  by ASBR11 to iPE using BGP-LU</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: Let's applying
              the above forwarding steps to the example described in
              Figure 1 Section 2.3.1.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: Let's applying
              the above forwarding steps to the example described in
              Figure 2 Section 2.3.1.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">(somewhat guesssing.
              But in all cases, there is no figure 1 in section 2.3.1)</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§4.1</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">IMO </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">OLD: As soon as the
              IGP convergence is effective for the BGP nhop entry, the
              new forwarding state is immediately available to all
              dependent BGP prefixes.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">NEW: As soon as the
              IGP convergence is effective for a BGP next-hop entry, the
              new forwarding state is immediately available to all
              dependent BGP prefixes.</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">more generally</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">:s/nhop/next-hop</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Replaced nhop with next-hop in the entire document<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">---</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">§4.3</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">:s/PE222/PE22</span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR">#Ahmed:
              Corrected<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Best regards,</span><o:p></o:p></p>
          <p class="MsoNormal"><span lang="EN-US">Bruno</span><o:p></o:p></p>
          <p class="MsoNormal"><strong><span
                style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> </span></strong><o:p></o:p></p>
          <pre>_________________________________________________________________________________________________________________________<o:p></o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre>Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
          <pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
          <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
          <pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre>This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></pre>
          <pre>they should not be distributed, used or copied without authorisation.<o:p></o:p></pre>
          <pre>If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></pre>
          <pre>As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></pre>
          <pre>Thank you.<o:p></o:p></pre>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;mso-fareast-language:FR"><o:p> </o:p></span></p>
        </div>
      </div>
      <pre>_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020502000109090102010808--


From nobody Mon Aug  1 19:34:01 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7D812D6AC for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 19:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level: 
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 pVx5YwssavXP for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 19:33:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1601B12B056 for <rtgwg@ietf.org>; Mon,  1 Aug 2016 19:33:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E3C90B8113A; Mon,  1 Aug 2016 19:33:57 -0700 (PDT)
To: Gabor.Sandor.Enyedi@ericsson.com, Andras.Csaszar@ericsson.com, akatlas@juniper.net, cbowers@juniper.net, abishek@ece.arizona.edu, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, cbowers@juniper.net, jefftant.ietf@gmail.com
Subject: [Technical Errata Reported] RFC7811 (4757)
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160802023357.E3C90B8113A@rfc-editor.org>
Date: Mon,  1 Aug 2016 19:33:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/OetkMRW4FK7DPXtPLZMuGDXKr3c>
Cc: rfc-editor@rfc-editor.org, dryan1008@aol.com, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 02:33:59 -0000

The following errata report has been submitted for RFC7811,
"An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7811&eid=4757

--------------------------------------
Type: Technical
Reported by: Ryan dun <dryan1008@aol.com>

Section: RFC7811

Original Text
-------------
Trying to block

Corrected Text
--------------


Notes
-----


Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)
--------------------------------------
Title               : An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)
Publication Date    : June 2016
Author(s)           : G. Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. Gopalan
Category            : PROPOSED STANDARD
Source              : Routing Area Working Group
Area                : Routing
Stream              : IETF
Verifying Party     : IESG


From nobody Mon Aug  1 19:35:31 2016
Return-Path: <akatlas@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34BC112D661 for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 19:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 hGWE6gnGNrxp for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 19:35:27 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0110.outbound.protection.outlook.com [104.47.37.110]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6A212B056 for <rtgwg@ietf.org>; Mon,  1 Aug 2016 19:35:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=H871BCA3bG3si+mzaf0Hbjo+j9oFD76TrWh7vAZn2zA=; b=Fbw+sSLYi9LD9pUmjW+3i7FtX7erLFyddNvr/6mIIxZDIy+dwnhSoDWlo0IkUo99LAGzwkWUmUKH4AbsenzZWR9ws4MGUVbGMsNQFsnxbxCqXM9+MZRKlmxhG4JKcZPDgrcS2VHSnLROktXO0BThfWX8LQmKUAeWrYBeLTW6Cc4=
Received: from BN3PR05MB2707.namprd05.prod.outlook.com (10.167.2.136) by BN3PR05MB2705.namprd05.prod.outlook.com (10.167.2.134) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.557.8; Tue, 2 Aug 2016 02:35:24 +0000
Received: from BN3PR05MB2707.namprd05.prod.outlook.com ([10.167.2.136]) by BN3PR05MB2707.namprd05.prod.outlook.com ([10.167.2.136]) with mapi id 15.01.0557.009; Tue, 2 Aug 2016 02:35:24 +0000
From: Alia Atlas <akatlas@juniper.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: RE: [Technical Errata Reported] RFC7811 (4757)
Thread-Topic: [Technical Errata Reported] RFC7811 (4757)
Thread-Index: AQHR7GZTKejZqfMYT02+G4DEySVdVaA09D5Y
Date: Tue, 2 Aug 2016 02:35:24 +0000
Message-ID: <92fgv2gpbq7to9edo96jpftp.1470105321013@email.android.com>
References: <20160802023357.E3C90B8113A@rfc-editor.org>
In-Reply-To: <20160802023357.E3C90B8113A@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=akatlas@juniper.net; 
x-originating-ip: [74.104.146.105]
x-ms-office365-filtering-correlation-id: 64d07f18-f9c9-44fd-0327-08d3ba7da837
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2705; 6:znKn/EEisEOwXzVuNtGfXN6hsgsoFPM13XqwQbU1Dsxcq/Munu1/6MG6wCekB4dtRGrSuOgV43bemgVQAUj4DgQN/Aa+COYZtXUre4ayS1WMV+InVoNTBJ0otgG4ETQGo57W05SKNPuNlHIoEoXvTkFvxff/njxeg0DYuHaEb8OaDRB31MGN0bZdx7tlZbIE1oEUpfXhrWqmO1J6GN1pgoAPSkL/iAlSaOTyEUmmH1TUqRyK/WVif7VqHltFznVtTUjzRxTao3BGhG64Y2YGUAIo77UU8dTi8F8sYM1MtjhZUE1gr1C8ZkQBaNHB+jxIwczq9j5O/PysimnblYyEMg==; 5:7nmjfzbT9+Cg/rmBTtB0G7QfCT9/g1fAm9h8NSlJNO7HD1qj5ZKpmlUr8PR4PxXHqxZ0BwUevQPlB9xi/TeibAsz0To4GWIhVQ0/qSSU6IlV1lPut9fYdQ6bC3ZY9mf9yotnvAwFdIvoXZQh79wDIA==; 24:auXLtvWkZSxMCpI78XgbznZe3fRyTqCt4VWtaNt0VgQG1XMqruE1bAXB1KTOu2qon8yXlmKTkJQm7Mg1am/XERe5lRn3NSJ88ItCxxHS02M=; 7:6PbYDjIrg6AfBqA+aMoM1P8D2gc4fgdWnYKQVlgnZqL1Mr3+Xi7h1IaZEouBHSCIVj6UFH5gKKzhZP2+6GsYasmae0EKt9QwQcwc2ArkW9g6J+0vquyR9dG6VHo6mDAb9I1bC3HGnzH6iv/gXtmubehz8etROHUeI616Aaozu6CA7qjm6qqsMsEUTvkje46F3ScQwgPnUXKHCL9dPa9MxHC0RW1wYOpmoKF1eb812HW78KpS+B/ueC75SS4lKlVx
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR05MB2705;
x-microsoft-antispam-prvs: <BN3PR05MB2705A670782ACD0F38D68EC3B5050@BN3PR05MB2705.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(158342451672863)(149059832740258)(138986009662008)(97927398514766)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026);  SRVR:BN3PR05MB2705; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2705; 
x-forefront-prvs: 0022134A87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(199003)(189002)(377454003)(110136002)(102836003)(9686002)(16236675004)(6116002)(3846002)(15975445007)(11100500001)(97736004)(99286002)(586003)(68736007)(19580395003)(76176999)(81156014)(8676002)(95246002)(16799955002)(3660700001)(9886003)(8936002)(7736002)(7846002)(7906003)(2950100001)(3280700002)(10400500002)(4326007)(5002640100001)(33646002)(2900100001)(106116001)(92566002)(19580405001)(81166006)(19625215002)(54356999)(105586002)(63666004)(66066001)(19617315012)(50986999)(86362001)(189998001)(101416001)(106356001)(2906002)(122556002)(77096005)(87936001)(15188155005)(51650200001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2705; H:BN3PR05MB2707.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_92fgv2gpbq7to9edo96jpftp1470105321013emailandroidcom_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2016 02:35:24.3025 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2705
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/w0vdNMJf5fvpNjlPDnbmeLJ497w>
Cc: "dryan1008@aol.com" <dryan1008@aol.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 02:35:30 -0000

--_000_92fgv2gpbq7to9edo96jpftp1470105321013emailandroidcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Spam, I believe.  Could you please delete?

Thanks,
Alia



Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: 8/1/16 10:34 PM (GMT-05:00)
To: Gabor.Sandor.Enyedi@ericsson.com, Andras.Csaszar@ericsson.com, Alia Atl=
as <akatlas@juniper.net>, Chris Bowers <cbowers@juniper.net>, abishek@ece.a=
rizona.edu, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, Chris Bow=
ers <cbowers@juniper.net>, jefftant.ietf@gmail.com
Cc: dryan1008@aol.com, rtgwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Technical Errata Reported] RFC7811 (4757)

The following errata report has been submitted for RFC7811,
"An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant T=
rees (MRT-FRR)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3D7811&eid=3D4757

--------------------------------------
Type: Technical
Reported by: Ryan dun <dryan1008@aol.com>

Section: RFC7811

Original Text
-------------
Trying to block

Corrected Text
--------------


Notes
-----


Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)
--------------------------------------
Title               : An Algorithm for Computing IP/LDP Fast Reroute Using =
Maximally Redundant Trees (MRT-FRR)
Publication Date    : June 2016
Author(s)           : G. Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. Gopala=
n
Category            : PROPOSED STANDARD
Source              : Routing Area Working Group
Area                : Routing
Stream              : IETF
Verifying Party     : IESG


--_000_92fgv2gpbq7to9edo96jpftp1470105321013emailandroidcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Spam, I believe. &nbsp;Could you please delete?&nbsp;</div>
<div><br>
</div>
<div>Thanks,&nbsp;</div>
<div>Alia&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id=3D"x_composer_signature">
<div dir=3D"auto" style=3D"font-size:88%; color:#364f67">Sent from my T-Mob=
ile 4G LTE Device</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: RFC Errata System &lt;rfc-editor@rfc-editor.org&gt; <br>
Date: 8/1/16 10:34 PM (GMT-05:00) <br>
To: Gabor.Sandor.Enyedi@ericsson.com, Andras.Csaszar@ericsson.com, Alia Atl=
as &lt;akatlas@juniper.net&gt;, Chris Bowers &lt;cbowers@juniper.net&gt;, a=
bishek@ece.arizona.edu, akatlas@gmail.com, db3546@att.com, aretana@cisco.co=
m, Chris Bowers &lt;cbowers@juniper.net&gt;, jefftant.ietf@gmail.com
<br>
Cc: dryan1008@aol.com, rtgwg@ietf.org, rfc-editor@rfc-editor.org <br>
Subject: [Technical Errata Reported] RFC7811 (4757) <br>
<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">The following errata report has been submitted for=
 RFC7811,<br>
&quot;An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redund=
ant Trees (MRT-FRR)&quot;.<br>
<br>
--------------------------------------<br>
You may review the report below and at:<br>
<a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D7811&amp;eid=
=3D4757">http://www.rfc-editor.org/errata_search.php?rfc=3D7811&amp;eid=3D4=
757</a><br>
<br>
--------------------------------------<br>
Type: Technical<br>
Reported by: Ryan dun &lt;dryan1008@aol.com&gt;<br>
<br>
Section: RFC7811<br>
<br>
Original Text<br>
-------------<br>
Trying to block<br>
<br>
Corrected Text<br>
--------------<br>
<br>
<br>
Notes<br>
-----<br>
<br>
<br>
Instructions:<br>
-------------<br>
This erratum is currently posted as &quot;Reported&quot;. If necessary, ple=
ase<br>
use &quot;Reply All&quot; to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary. <br>
<br>
--------------------------------------<br>
RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)<br>
--------------------------------------<br>
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; : An Algorithm for Computing IP/LDP Fast Reroute Using Maxim=
ally Redundant Trees (MRT-FRR)<br>
Publication Date&nbsp;&nbsp;&nbsp; : June 2016<br>
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : G. =
Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. Gopalan<br>
Category&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
: PROPOSED STANDARD<br>
Source&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; : Routing Area Working Group<br>
Area&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; : Routing<br>
Stream&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; : IETF<br>
Verifying Party&nbsp;&nbsp;&nbsp;&nbsp; : IESG<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_92fgv2gpbq7to9edo96jpftp1470105321013emailandroidcom_--


From nobody Mon Aug  1 21:28:48 2016
Return-Path: <mferguson@amsl.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99B812D0C2 for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 21:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.908
X-Spam-Level: 
X-Spam-Status: No, score=-3.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 DMylu5sYot_9 for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 21:28:45 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7108912D08C for <rtgwg@ietf.org>; Mon,  1 Aug 2016 21:28:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 671AF1E5D8D; Mon,  1 Aug 2016 21:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szhOnmPTVpes; Mon,  1 Aug 2016 21:25:51 -0700 (PDT)
Received: from [192.168.0.5] (cpe-76-174-176-44.socal.res.rr.com [76.174.176.44]) by c8a.amsl.com (Postfix) with ESMTPA id 097641E5D89; Mon,  1 Aug 2016 21:25:51 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [Technical Errata Reported] RFC7811 (4757)
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <20160802023357.E3C90B8113A@rfc-editor.org>
Date: Mon, 1 Aug 2016 21:28:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <80630023-31D9-4F51-AFBA-082724295672@amsl.com>
References: <20160802023357.E3C90B8113A@rfc-editor.org>
To: RFC System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/-v1G0ZeFbaHjLxT_yp09NdUWvAs>
Cc: db3546@att.com, akatlas@juniper.net, dryan1008@aol.com, abishek@ece.arizona.edu, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 04:28:47 -0000

Greetings,

FYI - This report has been removed.

Thank you.

RFC Editor/mf

On Aug 1, 2016, at 7:33 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC7811,
> "An Algorithm for Computing IP/LDP Fast Reroute Using Maximally =
Redundant Trees (MRT-FRR)".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D7811&eid=3D4757
>=20
> --------------------------------------
> Type: Technical
> Reported by: Ryan dun <dryan1008@aol.com>
>=20
> Section: RFC7811
>=20
> Original Text
> -------------
> Trying to block
>=20
> Corrected Text
> --------------
>=20
>=20
> Notes
> -----
>=20
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)
> --------------------------------------
> Title               : An Algorithm for Computing IP/LDP Fast Reroute =
Using Maximally Redundant Trees (MRT-FRR)
> Publication Date    : June 2016
> Author(s)           : G. Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. =
Gopalan
> Category            : PROPOSED STANDARD
> Source              : Routing Area Working Group
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>=20


From dryan1008@aol.com  Mon Aug  1 20:51:00 2016
Return-Path: <dryan1008@aol.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF94A12D10D for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 20:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_FONT_SIZE_HUGE=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mx.aol.com
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 ufKvIju1fryQ for <rtgwg@ietfa.amsl.com>; Mon,  1 Aug 2016 20:50:57 -0700 (PDT)
Received: from omr-m007e.mx.aol.com (omr-m007e.mx.aol.com [204.29.186.9]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3667612B05E for <rtgwg@ietf.org>; Mon,  1 Aug 2016 20:50:57 -0700 (PDT)
Received: from mtaomg-mcc01.mx.aol.com (mtaomg-mcc01.mx.aol.com [172.26.253.85]) by omr-m007e.mx.aol.com (Outbound Mail Relay) with ESMTP id 27AB638000BE; Mon,  1 Aug 2016 23:50:55 -0400 (EDT)
Received: from core-lec02a.mail.aol.com (core-lec02.mail.aol.com [10.76.11.12]) by mtaomg-mcc01.mx.aol.com (OMAG/Core Interface) with ESMTP id DED1E38000081;  Mon,  1 Aug 2016 23:50:54 -0400 (EDT)
Received: from 32.213.104.50 by webprd-a92.mail.aol.com (10.72.112.250) with HTTP (WebMailUI); Mon, 01 Aug 2016 23:50:54 -0400
Date: Mon, 1 Aug 2016 23:50:54 -0400
From: Ryanlovescheryl <dryan1008@aol.com>
To: akatlas@juniper.net, rfc-editor@rfc-editor.org
Message-Id: <15649602bf1-63ec-2aec@webprd-a92.mail.aol.com>
In-Reply-To: <92fgv2gpbq7to9edo96jpftp.1470105321013@email.android.com>
Subject: Re: [Technical Errata Reported] RFC7811 (4757)
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_13924_721439137.1470109854702"
X-MB-Message-Source: WebUI
X-MB-Message-Type: User
X-Mailer: JAS STD
X-Originating-IP: [32.213.104.50]
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1470109855; bh=1tTL3GP4lR1llec3lrNZkACX0Gz2xU9IhNWQD8ZyiYs=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=CH7acSSZH9/bWKRPzZMIIJmeNJoc8d36I/8JDq2Cf+yETDNZXTe9FPlPMDO6nIBf7 MxnQaRug8hGLN/ZjaQ32g+QVQ6kG5SHx+9Hlsqn7sY8LY2cPEtgDDMx6BiSVStdRmw ek0wq2bY/PSmBE2brHi3pddbnOrI2R14EPzm6CSo=
x-aol-sid: 3039ac1afd5557a0189e1d98
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/aij3YSQXsUnrb44byaGEej46sHU>
X-Mailman-Approved-At: Tue, 02 Aug 2016 09:45:04 -0700
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 03:53:43 -0000

------=_Part_13924_721439137.1470109854702
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Not sure how to


Ryanlovescheryl





-----Original Message-----
From: Alia Atlas <akatlas@juniper.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dryan1008 <dryan1008@aol.com>; rtgwg <rtgwg@ietf.org>
Sent: Mon, Aug 1, 2016 10:35 pm
Subject: RE: [Technical Errata Reported] RFC7811 (4757)



Spam, I believe.  Could you please delete? 


Thanks, 
Alia 







Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: RFC Errata System <rfc-editor@rfc-editor.org> 
Date: 8/1/16 10:34 PM (GMT-05:00) 
To: Gabor.Sandor.Enyedi@ericsson.com, Andras.Csaszar@ericsson.com, Alia Atlas <akatlas@juniper.net>, Chris Bowers <cbowers@juniper.net>, abishek@ece.arizona.edu, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, Chris Bowers <cbowers@juniper.net>, jefftant.ietf@gmail.com
Cc: dryan1008@aol.com, rtgwg@ietf.org, rfc-editor@rfc-editor.org 
Subject: [Technical Errata Reported] RFC7811 (4757) 


The following errata report has been submitted for RFC7811,
"An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7811&eid=4757

--------------------------------------
Type: Technical
Reported by: Ryan dun <dryan1008@aol.com>

Section: RFC7811

Original Text
-------------
Trying to block

Corrected Text
--------------


Notes
-----


Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)
--------------------------------------
Title               : An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)
Publication Date    : June 2016
Author(s)           : G. Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. Gopalan
Category            : PROPOSED STANDARD
Source              : Routing Area Working Group
Area                : Routing
Stream              : IETF
Verifying Party     : IESG




------=_Part_13924_721439137.1470109854702
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<font color=3D'black' size=3D'7' face=3D''Courier New', Courier, mono'>Not =
sure how to<br>
<br>

<div style=3D"clear:both">Ryanlovescheryl<br>
<br>
</div>
<br>
<br>

<div style=3D"font-family:arial,helvetica;font-size:10pt;color:black">-----=
Original Message-----<br>
From: Alia Atlas &lt;akatlas@juniper.net&gt;<br>
To: RFC Errata System &lt;rfc-editor@rfc-editor.org&gt;<br>
Cc: dryan1008 &lt;dryan1008@aol.com&gt;; rtgwg &lt;rtgwg@ietf.org&gt;<br>
Sent: Mon, Aug 1, 2016 10:35 pm<br>
Subject: RE: [Technical Errata Reported] RFC7811 (4757)<br>
<br>




<div id=3D"AOLMsgPart_2_34e1efdb-0586-4a70-b593-982c8e5e382b">
<style scoped=3D"">#AOLMsgPart_2_34e1efdb-0586-4a70-b593-982c8e5e382b td{co=
lor: black;}  .aolReplacedBody .EmailQuote { margin-left: 1pt; padding-left=
: 4pt; border-left: #800000 2px solid; } </style>
<div class=3D"aolReplacedBody">

<div>

<div>Spam, I believe. &nbsp;Could you please delete?&nbsp;</div>


<div><br>

</div>


<div>Thanks,&nbsp;</div>


<div>Alia&nbsp;</div>


<div><br>

</div>


<div><br>

</div>


<div><br>

</div>


<div id=3D"x_composer_signature">

<div dir=3D"auto" style=3D"font-size:88%; color:#364f67">Sent from my T-Mob=
ile 4G LTE Device</div>

</div>

<br>

<br>

-------- Original message --------<br>

From: RFC Errata System &lt;rfc-editor@rfc-editor.org&gt; <br>

Date: 8/1/16 10:34 PM (GMT-05:00) <br>

To: <a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:Ga=
bor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@ericsson.com</a>, <a re=
movedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:Andras.Csas=
zar@ericsson.com">Andras.Csaszar@ericsson.com</a>, Alia Atlas &lt;<a remove=
dlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:akatlas@juniper=
.net">akatlas@juniper.net</a>&gt;, Chris Bowers &lt;<a removedlink__be3dc82=
a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:cbowers@juniper.net">cbowers@=
juniper.net</a>&gt;, <a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__=
href=3D"mailto:abishek@ece.arizona.edu">abishek@ece.arizona.edu</a>, <a rem=
ovedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:akatlas@gmai=
l.com">akatlas@gmail.com</a>, <a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489=
cbc3ec7__href=3D"mailto:db3546@att.com">db3546@att.com</a>, <a removedlink_=
_be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:aretana@cisco.com">ar=
etana@cisco.com</a>, Chris Bowers &lt;<a removedlink__be3dc82a-b0fb-4e7f-b4=
ed-5a489cbc3ec7__href=3D"mailto:cbowers@juniper.net">cbowers@juniper.net</a=
>&gt;, <a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto=
:jefftant.ietf@gmail.com">jefftant.ietf@gmail.com</a>
<br>

Cc: <a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__href=3D"mailto:dr=
yan1008@aol.com">dryan1008@aol.com</a>, <a removedlink__be3dc82a-b0fb-4e7f-=
b4ed-5a489cbc3ec7__href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>, rfc-e=
ditor@rfc-editor.org <br>

Subject: [Technical Errata Reported] RFC7811 (4757) <br>

<br>

</div>

<font size=3D"2"><span style=3D"font-size:10pt;">

<div class=3D"PlainText">The following errata report has been submitted for=
 RFC7811,<br>

"An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant T=
rees (MRT-FRR)".<br>

<br>

--------------------------------------<br>

You may review the report below and at:<br>

<a target=3D"_blank" removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3ec7__hre=
f=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D7811&amp;eid=3D4757"=
>http://www.rfc-editor.org/errata_search.php?rfc=3D7811&amp;eid=3D4757</a><=
br>

<br>

--------------------------------------<br>

Type: Technical<br>

Reported by: Ryan dun &lt;<a removedlink__be3dc82a-b0fb-4e7f-b4ed-5a489cbc3=
ec7__href=3D"mailto:dryan1008@aol.com">dryan1008@aol.com</a>&gt;<br>

<br>

Section: RFC7811<br>

<br>

Original Text<br>

-------------<br>

Trying to block<br>

<br>

Corrected Text<br>

--------------<br>

<br>

<br>

Notes<br>

-----<br>

<br>

<br>

Instructions:<br>

-------------<br>

This erratum is currently posted as "Reported". If necessary, please<br>

use "Reply All" to discuss whether it should be verified or<br>

rejected. When a decision is reached, the verifying party (IESG)<br>

can log in to change the status and edit the report, if necessary. <br>

<br>

--------------------------------------<br>

RFC7811 (draft-ietf-rtgwg-mrt-frr-algorithm-09)<br>

--------------------------------------<br>

Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; : An Algorithm for Computing IP/LDP Fast Reroute Using Maxim=
ally Redundant Trees (MRT-FRR)<br>

Publication Date&nbsp;&nbsp;&nbsp; : June 2016<br>

Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : G. =
Enyedi, A. Csaszar, A. Atlas, C. Bowers, A. Gopalan<br>

Category&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
: PROPOSED STANDARD<br>

Source&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; : Routing Area Working Group<br>

Area&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; : Routing<br>

Stream&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; : IETF<br>

Verifying Party&nbsp;&nbsp;&nbsp;&nbsp; : IESG<br>

<br>

</div>

</span></font>


</div>

</div>




</div>
</font>
------=_Part_13924_721439137.1470109854702--


From nobody Tue Aug  2 14:42:22 2016
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B52612D99F; Tue,  2 Aug 2016 14:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8k8_sMVcmIVC; Tue,  2 Aug 2016 14:42:19 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 2253D12D9A1; Tue,  2 Aug 2016 14:41:56 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id h186so69891384pfg.3; Tue, 02 Aug 2016 14:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=UNbREmmteYz+dv/dsVXWwcy3N03VjlJAqqSALWfBWXM=; b=psxxsGUh0/cfVCIBBgbJ88FD4EjFuS9GcQSqHiSjUIcCS3Nxt9Zi+uZYK6YwVfdPL9 ph9vLjMqOmHvGPxyU918sKmS3Q/p/NKFtrsA5HwGOgCWMeyvhnvEDhsbksVGXgQK+zk1 7WSTbp9P5O3meoAgGBhk2ICXTMEhCbisCsjHEKVVcIe30AybBe47T95sis79B8oLuHIO e/GJgs/SOM711Xy37Vt/wMKYYkEr9zaKt5TOdl22X4xrduBAiOBHu2vJfa35mKPJyNBY hUv97/mHp0eEUV1HeWHMMPPuwWLBi6nbO9aKDDjxSK/nKr54bcayYXgpH0HHK5pxvYh/ ob0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=UNbREmmteYz+dv/dsVXWwcy3N03VjlJAqqSALWfBWXM=; b=ZOz/EhYBH8VMojhLlNa0FjHlm4L7gMtcJpV5HUzkK7n6qlwJbHULb0gvlQKPg22h4a mxF5Ywwageof5LjSSYAa1r6orYozaZpXrKmui5P5++1LJBMbaBhN3pwWtTZZrFpBPrek cM1EOtWAWAOLVD0wPBYBH55lrCjTCPCklnOAPtznTCoz0OY5DGmE3ZtZPMMPkdTxrEhb axl9ojmWTQS754gKT9KeXSvUv92/4GOVPIaY8FkyW1A8Fuws6iqnTy8VN7HPTGGXlUEv oPhLSpsgnaqqJA9exIqzZjgs1mGd0fGI2adRcOEPw5j5opQwCBDG2uI+VjaDh2cMKRVi 9fCg==
X-Gm-Message-State: AEkoous8PFUk3c/cYfrpSrz0+Qmgl/wvv19h3aEG1Ui6iAm2WiIA2UEX3POlEdxjup6fpg==
X-Received: by 10.98.210.69 with SMTP id c66mr109266807pfg.71.1470174115763; Tue, 02 Aug 2016 14:41:55 -0700 (PDT)
Received: from [192.168.253.142] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id w64sm7021473pfb.93.2016.08.02.14.41.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 14:41:55 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.17.0.160611
Date: Tue, 02 Aug 2016 14:41:54 -0700
Subject: FW: Request for WG adoption of  draft-psarkar-rtgwg-multihomed-prefix-lfa-04
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>
Message-ID: <8BA43138-CA9A-4FC0-8A8B-9DB726838730@gmail.com>
Thread-Topic: Request for WG adoption of  draft-psarkar-rtgwg-multihomed-prefix-lfa-04
References: <F17553F7-A619-439B-A3A5-95E034626C59@gmail.com> <35AD0717-E263-4960-AE9C-0FAA7A75E6CB@gmail.com> <3FE68ADF-8C6E-4E26-977C-441AD0880718@gredler.at>
In-Reply-To: <3FE68ADF-8C6E-4E26-977C-441AD0880718@gredler.at>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3552993715_1692935339"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/igDqoPHYiWIKI2C_uy-qwk3sLqQ>
Cc: draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 21:42:21 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3552993715_1692935339
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Proxiing for Hannes, who=E2=80=99s travelling.

=20

Cheers,

Jeff

=20

=20

From: Hannes Gredler <hannes@gredler.at>
Date: Tuesday, August 2, 2016 at 14:12
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: <draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org>
Subject: Re: Request for WG adoption of draft-psarkar-rtgwg-multihomed-pref=
ix-lfa-04

=20

not aware of any IPR except the disclosed one.



=20

From: Jeff Tantsura <jefftant.ietf@gmail.com>
Date: Monday, July 11, 2016 at 22:18
To: RTGWG <rtgwg@ietf.org>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org>, <draft-psarkar-rtgwg-multihomed-p=
refix-lfa@ietf.org>
Subject: Request for WG adoption of draft-psarkar-rtgwg-multihomed-prefix-l=
fa-04

=20

Dear RTGWG,

=20

The authors have requested the RTGWG to adopt draft-psarkar-rtgwg-multihome=
d-prefix-lfa-04 as the working group document.

=20

This draft has been present multiple times and no further comments are to b=
e addressed at this moment.=20

Please indicate support or no-support by July 30,, 2016.

=20

If you are listed as a document author or contributor please respond to thi=
s email stating of whether or not you are aware of any relevant IPR. The res=
ponse needs to be sent to the RTGWG mailing list. The document will not adva=
nce to the next stage until a response has been received from each author an=
d each individual that has contributed to the document.

=20

Thanks,

Jeff & Chris


--B_3552993715_1692935339
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Calibri;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>Proxiing for Hannes, who&#8217;s travelling.<o:p></o:p></span></p><div><p=
 class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Ch=
eers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;=
color:black'>Jeff<o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;bor=
der-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b=
><span style=3D'color:black'>From: </span></b><span style=3D'color:black'>Hannes=
 Gredler &lt;hannes@gredler.at&gt;<br><b>Date: </b>Tuesday, August 2, 2016 a=
t 14:12<br><b>To: </b>Jeff Tantsura &lt;jefftant.ietf@gmail.com&gt;<br><b>Cc=
: </b>&lt;draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org&gt;<br><b>Subje=
ct: </b>Re: Request for WG adoption of draft-psarkar-rtgwg-multihomed-prefix=
-lfa-04<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font=
-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p></div><div><div><div>=
<p class=3DMsoNormal>not aware of any IPR except the disclosed one.<o:p></o:p>=
</p></div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><br></p><=
/div><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div style=3D'border:none;border-top=
:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:black'>From: </span></b><span style=3D'color:black'>Jeff Tantsura=
 &lt;<a href=3D"mailto:jefftant.ietf@gmail.com">jefftant.ietf@gmail.com</a>&gt=
;<br><b>Date: </b>Monday, July 11, 2016 at 22:18<br><b>To: </b>RTGWG &lt;<a =
href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br><b>Cc: </b>rtgwg-chai=
rs &lt;<a href=3D"mailto:rtgwg-chairs@ietf.org">rtgwg-chairs@ietf.org</a>&gt;,=
 &lt;<a href=3D"mailto:draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org">dra=
ft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org</a>&gt;<br><b>Subject: </b>R=
equest for WG adoption of draft-psarkar-rtgwg-multihomed-prefix-lfa-04</span=
><o:p></o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family:"Time=
s New Roman"'>&nbsp;</span><o:p></o:p></p></div><div><div><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt'>Dear RTGWG,</span><o:p></o:p></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt'>The authors have requested the RTGW=
G to adopt draft-psarkar-rtgwg-multihomed-prefix-lfa-04 as the working group=
 document.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt'>This draft has been present multiple times and no further comments a=
re to be addressed at this moment. </span><o:p></o:p></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'>Please indicate support or no-support by July=
 30,, 2016.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt'>If you are listed as a document author or contributor please respon=
d to this email stating of whether or not you are aware of any relevant IPR.=
 The response needs to be sent to the RTGWG mailing list. The document will =
not advance to the next stage until a response has been received from each a=
uthor and each individual that has contributed to the document.</span><o:p><=
/o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</span><o:p=
></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Thanks,</span><=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Jeff &amp; C=
hris</span><o:p></o:p></p></div></div></div></blockquote></div></div></div><=
/body></html>

--B_3552993715_1692935339--



From nobody Tue Aug  2 14:42:37 2016
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676ED12D99B; Tue,  2 Aug 2016 14:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LU0NUDQY7zie; Tue,  2 Aug 2016 14:42:35 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 B601612D9A8; Tue,  2 Aug 2016 14:42:20 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id x72so70133978pfd.2; Tue, 02 Aug 2016 14:42:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=Hj4YwR0JPX9CHFtGzjWf3Ozu5EBwTDx/NyXYFgHp2+w=; b=fTCIxTKlm+uUgjXy0/cMnNRfq82lYOi2hiHeU04iYE+eIkxCDQZWIMDO3pLacXIDIx aCycFZnVfouiXDX43GJruIpKZrWEgBYkR2kcN97Ad+TE6Uq5dKt+5kCBi9qaDMNigLaX BPN4Y8nE7wUAngWVzzUxUhZPeC5nEIzJqcJI2iXY7KUpOvfmKRpXkZ567cggj+FPeIhk Rpl4eJOgcMKuCYGVGZ4Qq2Do+gfblI5b4NbB640CxOuoNGaqDL/cCj28rYl8qY1SCRQW jywya8WHcVzGMXubs58qwNGKZ435OggsJBkwzBQ90mE6iHRDN2gGAjBGqeptpfP8vy5I T8ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=Hj4YwR0JPX9CHFtGzjWf3Ozu5EBwTDx/NyXYFgHp2+w=; b=W8Xy4KfuRqsomGeOnLklidwwhOkYKG8RcpJXMvelPR8ramSc0D1dO6a8ZGBHmQNMxz iMyXBRjJOImjAZu82X3V5gG6PJDSmPQ1M88Pb6vlM5CKge4qKCp0HTlHBPb7SOW6wJa5 LO19K36DeyI9Dm6lMcB+0QFdWGZVNKsRxLN1cK653cl/3/9f1deasVpFE+asj4Dy7kZU 6YAaocL3ZEyXVhqGJCXMMLntC2mXXy2q8ay+yEtR55WSTXP6+JmeZpIRSYZvZJU7D02L D+nvb4JGHxqjQ6wFuqR+XTBTNe29fGC8xm+7mDkowvMRE8NYjRXPPV6GggQYX1LWLJTD XU+A==
X-Gm-Message-State: AEkoousr1wSZtds7KAGfkEb2W+gyEHthyDcquWfy9fhlDZXPZ2qHHTG3HiwI6piCqN2qCw==
X-Received: by 10.98.85.134 with SMTP id j128mr107255100pfb.6.1470174140182; Tue, 02 Aug 2016 14:42:20 -0700 (PDT)
Received: from [192.168.253.142] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id w64sm7021473pfb.93.2016.08.02.14.42.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 14:42:19 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.17.0.160611
Date: Tue, 02 Aug 2016 14:42:19 -0700
Subject: Re: Request for WG adoption of draft-psarkar-rtgwg-multihomed-prefix-lfa-04
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>
Message-ID: <51EE3176-8443-4AD7-8431-C31253FB8CD5@gmail.com>
Thread-Topic: Request for WG adoption of draft-psarkar-rtgwg-multihomed-prefix-lfa-04
References: <F17553F7-A619-439B-A3A5-95E034626C59@gmail.com> <CAEFuwkiq7q1pPVEqAZkS0CSGUU-jKPy=qzUixRa-SdvX8XQZHQ@mail.gmail.com>
In-Reply-To: <CAEFuwkiq7q1pPVEqAZkS0CSGUU-jKPy=qzUixRa-SdvX8XQZHQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3552993739_1629467522"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/lsWdxzIq8OwZoRxn2ALeUOmHtbk>
Cc: "draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org" <draft-psarkar-rtgwg-multihomed-prefix-lfa@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 21:42:36 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3552993739_1629467522
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Dear RTGWG,

=20

draft-psarkar-rtgwg-multihomed-prefix-lfa-04 has been adopted as the workin=
g group document.

Authors =E2=80=93 please re-publish accordingly.=20

=20

Thanks,

Jeff & Chris


On Tuesday, 12 July 2016, Jeff Tantsura <jefftant.ietf@gmail.com> wrote:

Dear RTGWG,

=20

The authors have requested the RTGWG to adopt draft-psarkar-rtgwg-multihome=
d-prefix-lfa-04 as the working group document.

=20

This draft has been presented multiple times and no further comments are to=
 be addressed at this moment.=20

Please indicate support or no-support by July 30,, 2016.

=20

If you are listed as a document author or contributor please respond to thi=
s email stating of whether or not you are aware of any relevant IPR. The res=
ponse needs to be sent to the RTGWG mailing list. The document will not adva=
nce to the next stage until a response has been received from each author an=
d each individual that has contributed to the document.

=20

Thanks,

Jeff & Chris


--B_3552993739_1629467522
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Calibri;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple><di=
v class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:Calibri'>Dear RTGWG,<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:Calibri'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:Calibri'>draft-psarka=
r-rtgwg-multihomed-prefix-lfa-04 has been adopted as the working group docum=
ent.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:Calibri'>Authors &#8211; please re-publish accordingly. <o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:Ca=
libri'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'font=
-size:10.5pt;font-family:Calibri;color:black'>Thanks,<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Calibri;color:bl=
ack'>Jeff &amp; Chris</span><o:p></o:p></p></div><div><p class=3DMsoNormal><br=
>On Tuesday, 12 July 2016, Jeff Tantsura &lt;<a href=3D"mailto:jefftant.ietf@g=
mail.com">jefftant.ietf@gmail.com</a>&gt; wrote:<o:p></o:p></p><blockquote s=
tyle=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;=
margin-left:4.8pt;margin-right:0in'><div><div><p class=3DMsoNormal style=3D'mso-=
margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0p=
t'>Dear RTGWG,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'><span style=3D'font-size:11.0pt'>The authors have reque=
sted the RTGWG to adopt draft-psarkar-rtgwg-multihomed-prefix-lfa-04 as the =
working group document.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-m=
argin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt=
'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt'>This draft ha=
s been presented multiple times and no further comments are to be addressed =
at this moment. </span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt'>Pleas=
e indicate support or no-support by July 30,, 2016.</span><o:p></o:p></p><p =
class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'fon=
t-size:11.0pt'>If you are listed as a document author or contributor please =
respond to this email stating of whether or not you are aware of any relevan=
t IPR. The response needs to be sent to the RTGWG mailing list. The document=
 will not advance to the next stage until a response has been received from =
each author and each individual that has contributed to the document.</span>=
<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'><span style=3D'font-size:11.0pt'>Thanks,</span><o:p></o:p></p><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'font-size:11.0pt'>Jeff &amp; Chris</span><o:p></o:p></p></div></div></block=
quote></div></div></body></html>

--B_3552993739_1629467522--



From nobody Tue Aug  2 14:51:31 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A944512D5D1; Tue,  2 Aug 2016 14:51:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-rtgyangdt-rtgwg-device-model-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802215125.27859.9825.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 14:51:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/rrbbq5iPPAvhD2nErqr5XoXfbU0>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 21:51:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : Network Device YANG Organizational Models
        Authors         : Acee Lindem
                          Lou Berger
                          Dean Bogdanovic
                          Christan Hopps
	Filename        : draft-rtgyangdt-rtgwg-device-model-05.txt
	Pages           : 22
	Date            : 2016-07-26

Abstract:
   This document presents an approach for organizing YANG models in a
   comprehensive structure that may be used to configure and operate
   network devices.  The structure is itself represented as a YANG
   model, with all of the related component models logically organized
   in a way that is operationally intuitive, but this model is not
   expected to be implemented.  The identified component modules are
   expected to be defined and implemented on common network devices.

   This document is derived from work submitted to the IETF by members
   of the informal OpenConfig working group of network operators and is
   a product of the Routing Area YANG Architecture design team.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-rtgyangdt-rtgwg-device-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-rtgyangdt-rtgwg-device-model-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-rtgyangdt-rtgwg-device-model-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Aug  2 15:13:18 2016
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5419012B061; Tue,  2 Aug 2016 15:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XYmMs-BnsaQO; Tue,  2 Aug 2016 15:13:14 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 294CE12D663; Tue,  2 Aug 2016 15:05:31 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id h186so70048912pfg.3; Tue, 02 Aug 2016 15:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=JET+rTFW3gBBQoOQ3KELlKG8vi3fv6SMeARHdAqRDGE=; b=jhhLACzYXQkz8IRTyuvr2+nJP9RbvK5MpJKUz46/tXhMUmt0jOyTpewguxiquxxOqN 7sIz8zwhKxOnT/8mFU4cG1beSj1uWTKaQUNZp89wTEM085GuXUx25rksnGECIuVbFHOz Giy+FBFvNkci1CG3Wqdyk9y6hbllatOgsczQIn7i+F6/rtm6o3kFo5wOXdZc1QUW+FdU U1Kf30wwiV0YJTjB22tRro+wI0pwN0dhrWWaq9QYd3x7WUee2BQbyhufa+Kh/U2MF0Ty e3wIAqzGfmf255svwjFZxC4SEaZCoPN++joeKfTKoZ+hBP0A4BUZxweVDQxnnFw7xOEG U1Vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=JET+rTFW3gBBQoOQ3KELlKG8vi3fv6SMeARHdAqRDGE=; b=kau29HSafcxTARXh+vyF6gnI1jHkqZcHjp4PnORZcqGHC9fat7JWdIpUzpGEsp4qlp tIpAjr2nvozcvwWCr9+aluGfMNiukLFvvt6SRkwHTzU5CpQHWME4+Jn7oq0UM/whwyUv EC1DsiMzd44p11ALdnPaNeZ6MdPgFXQnTsTktTsn2kKc6EcUrjBZIM7yRowDlq1zWQwr OBAooPOxWgyAd1kYynAEq/EC0j2C2PvrNBLr+uteoHaoHheBbSCGEWpKVIJ0xL3Txt0s fuiF/To/O0IMh9Ik1AOISAxOryTJuqACKl/vh061gOjAcR01KTYjxmTp0lU9Lw2m8/Us w0yw==
X-Gm-Message-State: AEkoouuE1yEM5BZQfSvxZquQhhsgjnLxVLZPDtsdTfVMgrk+eYc3vy3UcLr14Mz/bh9POQ==
X-Received: by 10.98.7.200 with SMTP id 69mr110133474pfh.33.1470175530583; Tue, 02 Aug 2016 15:05:30 -0700 (PDT)
Received: from [192.168.253.142] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id g5sm7133256pfg.0.2016.08.02.15.05.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 15:05:29 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.17.0.160611
Date: Tue, 02 Aug 2016 15:05:28 -0700
Subject: Re: working group adoption call for draft-rtgyangdt-rtgwg-device-model; draft-rtgyangdt-rtgwg-lne-model and draft-rtgyangdt-rtgwg-ni-model
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>
Message-ID: <37618A40-CAE4-4345-B56D-2685DE9702D5@gmail.com>
Thread-Topic: working group adoption call for draft-rtgyangdt-rtgwg-device-model; draft-rtgyangdt-rtgwg-lne-model and draft-rtgyangdt-rtgwg-ni-model
References: <8A056C97-7D5A-4A52-8D55-19BEC054E2BD@gmail.com> <D37CB272.63A59%acee@cisco.com> <7FC41664-36CC-4712-8FD0-B912391563ED@gmail.com> <565b3dfc-4edb-7f04-4565-f99f1e02661a@labn.net> <CE79123F-E8F7-4B25-9696-E6AFCEFB1CEE@gmail.com> <C67BC32F-DBA2-4F05-8BD1-E1A377A02C3D@gmail.com> <155896a6438.2818.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <155896a6438.2818.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/9zMCVzqc-YzvG9Pp7sL0v5r-IMo>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 22:13:15 -0000

Dear RTGWG,

draft-rtgyangdt-rtgwg-device-model has been adopted as the working group do=
cument.
Authors =E2=80=93 please re-publish accordingly.=20
=20
Thanks,
Jeff & Chris

 >> *From: *rtgwg <rtgwg-bounces@ietf.org <mailto:rtgwg-bounces@ietf.org>>
>> on behalf of Jeff Tantsura <jefftant.ietf@gmail.com
>> <mailto:jefftant.ietf@gmail.com>>
>> *Date: *Tuesday, June 7, 2016 at 5:12 PM
>> *To: *Routing WG <rtgwg@ietf.org <mailto:rtgwg@ietf.org>>
>> *Subject: *working group adoption call for
>> draft-rtgyangdt-rtgwg-device-model; draft-rtgyangdt-rtgwg-lne-model
>> and draft-rtgyangdt-rtgwg-ni-model
>>
>>
>>
>>     Dear RTGWG,
>>
>>
>>
>>     The authors have requested the RTGWG to adopt:
>>
>>     draft-rtgyangdt-rtgwg-device-model;
>>     draft-rtgyangdt-rtgwg-lne-model and draft-rtgyangdt-rtgwg-ni-model
>>     as working group documents.
>>
>>
>>
>>     There was good support during the last IETF meeting.
>>
>>     Please indicate support or no-support by June 22nd, 2016.
>>
>>
>>
>>     If you are listed as a document author or contributor please
>>     respond to this email stating of whether or not you are aware of
>>     any relevant IPR. The response needs to be sent to the RTGWG
>>     mailing list. The document will not advance to the next stage
>>     until a response has been received from each author and each
>>     individual that has contributed to the document.
>>
>>
>>
>>     Thanks,
>>
>>
>>
>>     Jeff & Chris
>>
>>
>>
>>
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>
>
>
>
>
>
>
>
>






From nobody Tue Aug  2 15:41:28 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 147DA12D9F5; Tue,  2 Aug 2016 15:41:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-device-model-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802224118.27802.34557.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 15:41:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4HG0tNsdziOt6SYPG-m2e52iVxU>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 22:41:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : Network Device YANG Organizational Models
        Authors         : Acee Lindem
                          Lou Berger
                          Dean Bogdanovic
                          Christan Hopps
	Filename        : draft-ietf-rtgwg-device-model-00.txt
	Pages           : 22
	Date            : 2016-08-02

Abstract:
   This document presents an approach for organizing YANG models in a
   comprehensive structure that may be used to configure and operate
   network devices.  The structure is itself represented as a YANG
   model, with all of the related component models logically organized
   in a way that is operationally intuitive, but this model is not
   expected to be implemented.  The identified component modules are
   expected to be defined and implemented on common network devices.

   This document is derived from work submitted to the IETF by members
   of the informal OpenConfig working group of network operators and is
   a product of the Routing Area YANG Architecture design team.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-device-model-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Aug  4 16:39:10 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD3212B053; Thu,  4 Aug 2016 16:39:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-multihomed-prefix-lfa-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160804233905.15924.11559.idtracker@ietfa.amsl.com>
Date: Thu, 04 Aug 2016 16:39:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/6kepxS78oHxv_rSasZSUHiLYxhQ>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2016 23:39:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : LFA selection for Multi-Homed Prefixes
        Authors         : Pushpasis Sarkar
                          Shraddha Hegde
                          Chris Bowers
                          Uma Chunduri
                          Jeff Tantsura
                          Bruno Decraene
                          Hannes Gredler
	Filename        : draft-ietf-rtgwg-multihomed-prefix-lfa-00.txt
	Pages           : 16
	Date            : 2016-08-04

Abstract:
   This document shares experience gained from implementing algorithms
   to determine Loop-Free Alternates for multi-homed prefixes.  In
   particular, this document provides explicit inequalities that can be
   used to evaluate neighbors as a potential alternates for multi-homed
   prefixes.  It also provides detailed criteria for evaluating
   potential alternates for external prefixes advertised by OSPF ASBRs.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-multihomed-prefix-lfa/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-multihomed-prefix-lfa-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Aug 10 06:57:44 2016
Return-Path: <nitisgup@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3962B12D59F; Wed, 10 Aug 2016 06:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level: 
X-Spam-Status: No, score=-15.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 vaMiVWVctWf4; Wed, 10 Aug 2016 06:57:40 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E95612D53D; Wed, 10 Aug 2016 06:57:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1394; q=dns/txt; s=iport; t=1470837460; x=1472047060; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=lynrpq8hK3OfbaHWNAFWzp4STf15UB9HDDUBfKtiepQ=; b=FRCnA8Afbj+pIwUHw3fEQLMe6g6HfAhsYpoGboT6xkXv1U5uDkmdmZ6x qzwM1Z1/871dL5kcND6+A/LTOXY5WIPsEBWbDt9WyxBx/GQQNgYY1l/XM RQ2dnIBmynEtqF07YKe6+hvtWM7hHlAb5VTiWGigGhwIl7vgGndeYovUP g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ASAgCLMqtX/4ENJK1dg0VWfAe5H4F9J?= =?us-ascii?q?IV5AoFeOBQBAQEBAQEBXSeEXwEFOj0CEAIBCDYQMiUCBAENBYgxDsFsAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBHIYqhE2EQIVbAQSOGYsjAYYciHWBa06EDYh9jDSDd?= =?us-ascii?q?wEeNoN6bgGGIH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,500,1464652800"; d="scan'208";a="309027208"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Aug 2016 13:57:16 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u7ADvGVo003206 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Aug 2016 13:57:16 GMT
Received: from xch-rtp-003.cisco.com (64.101.220.143) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 10 Aug 2016 09:57:15 -0400
Received: from xch-rtp-003.cisco.com ([64.101.220.143]) by XCH-RTP-003.cisco.com ([64.101.220.143]) with mapi id 15.00.1210.000; Wed, 10 Aug 2016 09:57:15 -0400
From: "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>,  "cbowers@juniper.net" <cbowers@juniper.net>, "Alexander.Vainshtein@ecitele.com" <Alexander.Vainshtein@ecitele.com>
Subject: Re: New Version Notification for draft-nitish-vrrp-bfd-04.txt
Thread-Topic: New Version Notification for draft-nitish-vrrp-bfd-04.txt
Thread-Index: AQHR8w2xKuf6NoDGmUqiwL1JzEjBsKBC11SA
Date: Wed, 10 Aug 2016 13:57:15 +0000
Message-ID: <D3D12E58.6A393%nitisgup@cisco.com>
References: <147083682806.20485.10861528246457996725.idtracker@ietfa.amsl.com>
In-Reply-To: <147083682806.20485.10861528246457996725.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.232.12.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5F4B88C7987083478125D7AED59099A7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4qU3W1eDZUh-hWrjakk-adfcB-k>
Cc: Greg Mirsky <gregory.mirsky@ericsson.com>, Jeff Haas <jhaas@juniper.net>, Colin Docherty <colin@doch.org.uk>, "Aditya Dogra \(addogra\)" <addogra@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 13:57:42 -0000

Hi Chris/Alexander,

Thanks a lot for your comments and suggestions on the draft.
We have incorporated all the comments given by you in the latest version.
Looking forward to your review of the Draft.



Thanks,
Nitish

On 10/08/16 7:17 pm, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-nitish-vrrp-bfd-04.txt
>has been successfully submitted by Nitish Gupta and posted to the
>IETF repository.
>
>Name:		draft-nitish-vrrp-bfd
>Revision:	04
>Title:		Fast failure detection in VRRP with BFD
>Document date:	2016-08-10
>Group:		Individual Submission
>Pages:		27
>URL:           =20
>https://www.ietf.org/internet-drafts/draft-nitish-vrrp-bfd-04.txt
>Status:         https://datatracker.ietf.org/doc/draft-nitish-vrrp-bfd/
>Htmlized:       https://tools.ietf.org/html/draft-nitish-vrrp-bfd-04
>Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-nitish-vrrp-bfd-=
04
>
>Abstract:
>   This document describes how Bidirectional Forwarding Detection (BFD)
>   can be used to support sub-second detection of a Master Router
>   failure in the Virtual Router Redundancy Protocol (VRRP).
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Wed Aug 10 09:05:36 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B16212D526; Wed, 10 Aug 2016 09:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 0mZ7DeoXgQw0; Wed, 10 Aug 2016 09:05:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11C2A12B036; Wed, 10 Aug 2016 09:05:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 026F0B80FC9; Wed, 10 Aug 2016 09:05:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7938 on Use of BGP for Routing in Large-Scale Data Centers
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160810160529.026F0B80FC9@rfc-editor.org>
Date: Wed, 10 Aug 2016 09:05:28 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/EG2lqLF29HkRqtnEDR7CvQ6UxuE>
Cc: drafts-update-ref@iana.org, rtgwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 16:05:30 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7938

        Title:      Use of BGP for Routing 
                    in Large-Scale Data Centers 
        Author:     P. Lapukhov, A. Premji,
                    J. Mitchell, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       August 2016
        Mailbox:    petr@fb.com, 
                    ariff@arista.com, 
                    jrmitche@puck.nether.net
        Pages:      35
        Characters: 89682
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-bgp-routing-large-dc-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7938

        DOI:        http://dx.doi.org/10.17487/RFC7938

Some network operators build and operate data centers that support
over one hundred thousand servers.  In this document, such data
centers are referred to as "large-scale" to differentiate them from
smaller infrastructures.  Environments of this scale have a unique
set of network requirements with an emphasis on operational
simplicity and network stability.  This document summarizes
operational experience in designing and operating large-scale data
centers using BGP as the only routing protocol.  The intent is to
report on a proven and stable routing design that could be leveraged
by others in the industry.

This document is a product of the Routing Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Thu Aug 11 18:40:00 2016
Return-Path: <rjs@rob.sh>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1026B127058; Thu, 11 Aug 2016 18:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=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 lS3VWLU5Nm-O; Thu, 11 Aug 2016 18:39:55 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2a03:9800:10:4c::cafe:b00c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F5C112D11D; Thu, 11 Aug 2016 18:39:54 -0700 (PDT)
Received: from [2602:4b:a27f:3000:39cd:2401:dd01:e1a0] by cappuccino.rob.sh with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <rjs@rob.sh>) id 1bY1Re-0000LN-9P; Fri, 12 Aug 2016 02:39:34 +0100
From: Rob Shakir <rjs@rob.sh>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Document Shepherd Review of draft-ietf-rtgwg-bgp-pic-02
Date: Thu, 11 Aug 2016 19:39:47 -0600
Message-Id: <C58CC6E1-763D-4D2A-A583-E3AFCC30B0F9@rob.sh>
To: draft-ietf-rtgwg-bgp-pic.all@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/HcnPlkzGaybeLkaKETPes_NfxFo>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2016 01:39:58 -0000

Ahmed, Clarence, Pradosh,

I did a review of draft-ietf-rtgwg-bgp-pic-02 as part of the process of =
doing a shepherd write-up for this document. I have a number of comments =
which I want to try and address first.

General:

1) This document feels really difficult to get the concepts from to me. =
The key intent (in my view) is to describe the way that one can =
structure a FIB to be able to reduce the number of updates that are =
required to reconverge. Unfortunately, the extensive use of examples (to =
me) does not make the core concepts that are being described =
super-clear. To this end, what I would propose is re-working the =
overview section. In this section the two =E2=80=9Cpillars=E2=80=9D that =
are described can be outlined in more detail. For example:

	BGP PIC is based on two FIB design concepts:
=09
	  1. Rather than implementing a forwarding construct each BGP =
NLRI has
	     a corresponding next-hop property, the FIB is implemented =
as a series of linked
	     entries, whereby many BGP NLRIs can link to a single =
next-hop entry (or set of
             next-hop entries).

	  2. Forwarding entries are represented as a chain - which may =
have multiple
	     levels of hierarchy representing the forwarding =
dependencies for packets
	     matching that criteria, for example, allowing a BGP NLRI to =
map to a BGP
	     next-hop which itself maps to an IGP next-hop, which maps =
to an interface.

	Designing the FIB in this manner allows commonalities between =
different prefixes
	to be exploited to improve convergence time. Particularly, where =
a particular
	element is updated (e.g., IGP path to a BGP next-hop), then =
these changes are
	inherited by the other entries which are linked to the updated =
element (i.e.,
	all BGP NLRIs which share the BGP next-hop above).

This high-level overview then allows a reader to be able parse *what* is =
really implemented prior to getting stuck into the detailed examples and =
walk-throughs. Defining this high-level approach would also help with =
the definitions section, such that there is some context before trying =
to understand the definitions.

2) The =E2=80=9CProperties=E2=80=9D section feels misplaced to me =E2=80=94=
 it seems to be a back reference to the rest of the document, whereas it =
would feel more natural if it were a description of the benefits of =
implementing the concepts that are described in the document, and a link =
to the sections where these are described in more detail.

Section 4 has a similar issue, insofar that it now informs us of how to =
implement some specifics of the actual forwarding behaviour following a =
number of examples. I=E2=80=99d propose that the layout of the document =
should be something more like:

	Intro =E2=80=94 why do we need PIC?
	Overview =E2=80=94 what is PIC?
		a) FIB layout
		b) FIB operation with PIC
		c) Dealing with limited hierarchy FIBs
	Characteristics of PIC - what does PIC require, what does it not =
require?
	Examples - demonstrating how PIC deals with various scenarios.
		a) Basic example (as per Figure 2)
			- Operation with iPE link failure
			- Operation with remote link failure in the core
			- Operation with ePE failure
			- Operation with ePE-CE link failure
		b) Optionally have the more complex example here.

3) Use of the phrase =E2=80=9CPrefix Independent Convergence=E2=80=9D. I =
understand that this is an established concept, which is widely =
implemented, however, if we are trying to be more technically robust =
then I think that we need to work on how this document describes the =
advantages of the methods that it proposes. In a network that has 1:1 =
mapping of prefix to next-hop then the mechanisms that are provided do =
not really mean that convergence is =E2=80=9Cprefix independent=E2=80=9D. =
A more robust way to describe this (IMHO) is that convergence time is =
now related to the number of next-hop updates that need to be made, =
rather than the number of NLRI. So - in the case that we have our 1:1 =
mapping of prefix to next-hop, then we describe the number of updates we =
need to make is still # of prefixes =3D=3D # of next-hops. However, =
since we expect prefix to next-hop to be N:1 in most cases, then we =
decouple of total number of *prefix* entries, but we=E2=80=99re still =
coupled to the number of next-hops. I=E2=80=99d encourage that if =
we=E2=80=99re going to have this document as output of the RTG WG then =
we are a little more robust in describing the characteristics of the =
solution - even if it does not sound quite so marketing-friendly as =
=E2=80=9Cprefix independent=E2=80=9D.

4) Examples =E2=80=94 in the doc, there is quite a lot of text which =
describes - in words - what the routing table looks like for certain =
scenarios. It was my feeling reviewing the document that actually adding =
this wording makes the examples difficult to understand. Could one =
rather describe the RIB by writing out what the entries would look like, =
or putting it in the context of each device. It might be worth trying to =
use some actual documentation prefixes in the examples, rather than the =
current approach, which creates some confusion as to what kind of =
information is being represented by the notation used.

For instance, Figure 2 feels more readable to me if written as follows:


           +--------------------------------+
           |                                |
           |                               ePE2 (loopback 192.0.2.1)
           |                                |  \
           |                                |   \
           |                                |    \
          iPE                               |    CE.......VRF "Blue"
           |                                |    /       (VPN-IP1 - =
65000:1:2001:DB8:1::/64)
           |                                |   /        (VPN-IP2 - =
65000:1:2001:DB8:2::/64)
           |   LDP/Segment-Routing Core     |  /
           |                               ePE1 (loopback 192.0.2.2)
           |                                |
           +--------------------------------+


	iPE=E2=80=99s routing table:
=09
		65000:1:2001:DB8:1::/64
			via ePE1 (192.0.2.1), VPN Label: VPN-L11
			via ePE2 (192.0.2.2), VPN Label:VPN-L21

		65000:1:2001:DB8:2::/64
			via ePE1 (192.0.2.1), VPN Label: VPN-L12
			via ePE2 (192.0.2.2), VPN Label: VPN-L22

		192.0.2.1/32
			via Core, Label: 		IGP-L11
			via Core, Label:		IGP-L12
=09
		192.0.2.2/32
			via Core, Label:		IGP-L21
			via Core, Label:		IGP-L22


Tabulating the routing information then makes it much easier to refer to =
in the subsequent diagram of the FIB layout.

5) In Section 3.2 - it seems like we go into a lot of detail of quite a =
complex forwarding topology to explain the idea of how we can flatten =
entries together in FIB hierarchy. I would propose that some text is =
added (ideally in the same section as the proposal in 1)  that describes =
the fundamentals of this section. It also does not seem clear from the =
text (or the diagrams) what the =E2=80=9C0=E2=80=9D and =E2=80=9C1=E2=80=9D=
 in the pathlist and then subsequent flattened pathlist actually =
represent? Are these next-hop IP addresses, or are they labels, or =
something different? (I presume that they are next-hop addresses, but =
this doesn=E2=80=99t seem super-evident).

6) There are some assertions in this document which I think are quite =
implementation specific:
	- 50msec failure detection of links =E2=80=94 one could indicate =
that this might be a typical time, but nothing in the mechanism that is =
described in this document guarantees this.
	- =E2=80=9CPerspective=E2=80=9D - 6.2.1 =E2=80=94 I think quite =
a few things here depend on how the implementation works. I would say =
that this section would be best moved to an appendix as something that =
demonstrates the potential advantages based on some example =
implementation and network topology.

At the moment, this feels like marketing numbers rather than anything =
that I=E2=80=99d really expect to be in a technical publication from =
this WG.

Specifics:

1) OutLabel-List: There is a definition here that says that the array =
can be of =E2=80=9Cone or more outgoing labels and/or label actions=E2=80=9C=
, there is no provision within this definition that the label can be =
unlabelled (or a no-op) - but this is clearly implemented and used in a =
later example. I presume it should be included in this definition.

2) The definition of dependency seems to say that an object X is =
dependent on object Y if Y can=E2=80=99t be deleted without X not being =
a dependency. It seems to me like we might want to make this definition =
less self-referential in the text. Perhaps something akin to:

	One object X is determined to be a dependent of another object Y =
if a link within
	a specified forwarding chain exists between the two objects.

3) Definition of primary path =E2=80=94 the definition here states that =
the path =E2=80=9Ccan be used all the time=E2=80=9D. However, we have =
cases where the primary BGP path cannot be used because the next-hop is =
unreachable in the IGP (for example). I think the definition stating =
that path can be used all the time is not correct, and rather one wants =
to indicate that the primary path is the first usable path within a path =
list or similar.

4) Definition of path =E2=80=94 the definition here states that the path =
is the =E2=80=9Cnext hop in a sequence of unique connected nodes=E2=80=9D.=
 Is this really what we mean - that a path needs to represent A-B-C-D. =
This doesn=E2=80=99t seem to tally with the definition (and use) of =
PathList which is simply the next-hop. Is a more rigorous definition =
that the a Path is an entry that corresponds to the first hop (i.e., the =
local device=E2=80=99s next-hop) of a series of nodes that end at the =
destination prefix?

5) Figure 3: It=E2=80=99s generally unclear to me what this figure is =
trying to show with some of the arrows. We have VPN-L11 which is (I =
assume) an ingress LFIB entry, and then VPN-IP1 which is an ingress IP =
leaf (within a VRF, I presume). What do the arrows from the top to the =
bottom indicate?

6) =E2=80=9CBGP is inherently slow=E2=80=9D =E2=80=94 this seems to =
require some subjective view of what =E2=80=98slow=E2=80=99 is. Would it =
not be better to state that the speed of convergence of BGP is limited =
by the time taken to serially propagate reachability information from =
the point of failure to the device that must reconverge.=20

7) =E2=80=9CAnother more common and widely deployed scenario is L3VPN=E2=80=
=9D =E2=80=94 do you want to state that this is another *common* =
deployment scenario, otherwise, what is this L3VPN deployment more =
common than?

8) There are some statements that this is =E2=80=9Cenabled with zero =
operator intervention=E2=80=9D =E2=80=94 it is probably enabled by some =
software upgrade, so I=E2=80=99m not sure that this is quite zero =
operator intervention - however, given that this is mentioned, do you =
also need to discuss why this is something that can be done on a =
per-node basis and what the potential negative impacts could be (if any) =
of this happening? In general, having new things turn on by default and =
not being able to test them, or know that they=E2=80=99ve changed is not =
a good way to ensure that you can resolve faults in a network swiftly =
and effectively.

9) (nit) Through the =E2=80=9Cterminology=E2=80=9D section - the =
definitions probably don=E2=80=99t need to start with =E2=80=9Cit is=E2=80=
=9D - one can simply say =E2=80=9CBGP prefix: A prefix p/m=E2=80=A6=E2=80=9D=
.

10) (nit) Forwarding Chain is inconsistently capitalised. Where it is =
capitalised, I expected to be able to find the definition in terminology =
- I=E2=80=99d suggest making this consistent.

11) In Section 5. there are a number of references to software =
components of the device that is then referenced throughout this =
section. It would be useful to define what those software components are =
- i.e., we have a BGP process which does X, an IGP process which does Y, =
and then a FIB manager process that does Z.

I appreciate that there are quite a lot of comments here, so happy to =
discuss this. I=E2=80=99d appreciate seeing some of them addressed =
before this draft progresses to IESG though.

Thanks!
r.=


From nobody Wed Aug 17 11:00:11 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A473F12D830; Wed, 17 Aug 2016 11:00:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-yang-key-chain-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147145681067.23809.5815994777670871873.idtracker@ietfa.amsl.com>
Date: Wed, 17 Aug 2016 11:00:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Mu_RI7IAyJMIkcFmGR9DQXAIzn8>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 18:00:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : Routing Key Chain YANG Data Model
        Authors         : Acee Lindem
                          Yingzhen Qu
                          Derek Yeung
                          Ing-Wher Chen
                          Jeffrey Zhang
                          Yi Yang
	Filename        : draft-ietf-rtgwg-yang-key-chain-07.txt
	Pages           : 21
	Date            : 2016-08-17

Abstract:
   This document describes the key chain YANG data model.  A key chain
   is a list of elements each containing a key, send lifetime, accept
   lifetime, and algorithm.  By properly overlapping the send and accept
   lifetimes of multiple key chain elements, keys and algorithms may be
   gracefully updated.  By representing them in a YANG data model, key
   distribution can be automated.  Key chains are commonly used for
   routing protocol authentication and other applications.  In some
   applications, the protocols do not use the key chain element key
   directly, but rather a key derivation function is used to derive a
   short-lived key from the key chain element key.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-yang-key-chain-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-yang-key-chain-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Aug 19 10:08:09 2016
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0F812D5F0; Fri, 19 Aug 2016 10:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.906
X-Spam-Level: 
X-Spam-Status: No, score=-101.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_10_20=0.093, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PyFMxBSp3LxU; Fri, 19 Aug 2016 10:07:59 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 6CD6A12D586; Fri, 19 Aug 2016 10:07:56 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id 97so90403618uav.3; Fri, 19 Aug 2016 10:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=PtlG4VgU6xZmk801MbQ/nVodK1DseZKWugF2pOKP85k=; b=mJbLNdpAwcMNvGFyoSpSkChEPZwd10DDA3ZDKYzA/MYzENmcOQfR67TRGo9uIXhKCf Xarq9TSL7et4FE0qbOY2JVzsPghXeUpRbtN56FKx/pRjfMdgiB12Vs6MJlJoUE9ABu0U 5AUXq0arh4V5x2r9B3bZCYeLVZDFqqomzW4en0d2iStJSDVaDz3E4YvAmpKzQbk0WSq+ 0Y9KoAwyf1GfV2TB7moRJimfRTkOFOl9M5K+v3FqB+l9pT4dOZUXVdiQ+1IvGt0wgM/P uPQVtKiaC1fYVXGZeGrRDnO3FZya1es/mekf1VLI5DbEyMS1xrXJUb/U4JiA8yCJC99B jHeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PtlG4VgU6xZmk801MbQ/nVodK1DseZKWugF2pOKP85k=; b=czdVvD/CSzWYu73DPs5QAMlrNcN5TxCaLewLIvN5TA38Z0uMC7+HxUWFwyTxzNcGY3 nElu+7y2ApA3pW7t5950siqlqhIWOfWs4RSsPmBFohvmIn06x2dxN6gsPUTA1IbP9wJe HRN3HQmf8sW+vGhqgdZnMFnU+P3BNhYwws9F4/l4K88NMTrazY/8SQEJCwTbqyKNsiw8 QTjIJP1+yFd8hN9THu7r0UhbiDyZ1riqw1pHHVhYToR4GVcqGbsucFZH8dBjTpVBBoBJ pXBu85rQD3pdkvwI5bUeUhdTDbtu5P9tjXqraT3BFhqmMKVQpZC9NiRAz6vZYJ//UPw+ EE/g==
X-Gm-Message-State: AEkooutfMZYWgKDX3TAFBWOQHdLvmgiBr4vkdj4tJ05TSqmVnKvxXRaYcfdZtIsCtLZ2rZW9HL/f5SRpogRFjw==
X-Received: by 10.159.39.228 with SMTP id b91mr4799082uab.41.1471626475276; Fri, 19 Aug 2016 10:07:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.50.7 with HTTP; Fri, 19 Aug 2016 10:07:54 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 19 Aug 2016 13:07:54 -0400
Message-ID: <CAG4d1restkyqtSHPeApNkVj18ARbsszmMRHxBnjUeV3L3bWe0A@mail.gmail.com>
Subject: Reorganizing & updating the Routing Yang Architecture Design Team
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>,  "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1244b64d10cc053a6fbd96
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/RFaWC_ikeBD7zTZd01aVo_ui4Vs>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 17:08:02 -0000

--94eb2c1244b64d10cc053a6fbd96
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In March 2015, I created the Routing Yang Architecture Design Team and
specified a charter
<https://www.ietf.org/mail-archive/web/routing-discussion/current/msg02000.=
html>
.
The Design Team has done some excellent work helping to steer and define
the work being done.  This includes draft-ietf-rtgwg-device-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>,
draft-ietf-rtgwg-lne-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>, and
draft-ietf-rtgwg-ni-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> as well as
identifying issues and work needed to be done in NetMod around improving
YANG, such as schema mount and opstate/revised datastores.

At this point, 17 months in, it is time to reorganize the DT a bit, set
additional goals, say thank you to some members and add some others who are
interested.

Going forward, the Design Team will focus on:

*Conventions as specified in the original charter* : Common conventions and
use of YANG   functionality in similar ways can help make the interactions
of models easier to understand.  RFC 6087 provides some guidance; an update
is underway now in draft-ietf-netmod-rfc6087bis.  If the design team has
recommendations for how the models should be written, those which are not
routing-specific can be written down and discussed in netmod.

*Ideas for how to handle extensions and features as specified in the
original charter*:

It is also important to consider how future extensibility and features in
Routing Area work will need to be captured inYANG models.  While the IETF
is busy developing YANG models, we are still working on new routing area
features and technology.  The design team should publish and maintain best
current practices for how new features can easily augment existing YANG mod=
els
so that authors of those new features and technologies can understand how
to consider YANG modeling.

*Classification*:  The ability to specify metadata for classification and
manipulation of models is being defined in draft-ietf-netmod-yang-mode
l-classification-02
<https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classificati=
on/>.
The DT will suggest classifications for Routing Area YANG models and
encourage consistency.

*Support work based on requirements*:  The DT will continue to support work
based on requirements from its previous work.  Examples of such work
include
draft-ietf-netmod-schema-mount-02
<https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/> and
opstate/revised datastores.

*Progress WG Drafts authored*:  The DT and the specific draft authors will
push to publication of the existing drafts: draft-ietf-rtgwg-device-model-0=
0
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>,
draft-ietf-rtgwg-lne-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>, and
draft-ietf-rtgwg-ni-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> .

*Consistency of Models across the Routing Area*:  The DT will look at
YANG models
in the Routing Area and encourage that common parts be factored out into
reusable models.  The DT will look at how well the set of models will work
together and raise any related issues.  There will be a particular focus on
models expected to progress to RFC in the next 12 months.

*Device Profiles of Needed Models:*  Different devices will need different
sets of YANG models for common operations.  There have been some initial
drafts (e.g. draft-faq-netmod-cpe-yang-profile-00.txt
<https://www.ietf.org/archive/id/draft-faq-netmod-cpe-yang-profile-00.txt>)
in this space.  The DTwill provide guidance for what is needed in a device
profile, as far as the Routing Area aspects, are concerned and facilitate
the creation of appropriate device profiles.  This should aid in
determining what groups of models are needed for practical use for
particular device roles.

The Design Team members will include:

Lou Berger <=E2=80=8Blberger@labn.net>  (lead)
Acee Lindem <=E2=80=8Bacee@cisco.com>
Christian Hopps <=E2=80=8Bchopps@chopps.org>
Dean Bogdanovic <=E2=80=8Bdeanb@juniper.net>
Rob Shakir <=E2=80=8Brjs@rob.sh>
Anees Shaikh <=E2=80=8Baashaikh@google.com>
Qin Wu <=E2=80=8Bbill.wu@huawei.com>
Ebben Aries  <exa@juniper.net>
Yingzhen Qu <yiqu@cisco.com>
Xufeng Liu <xliu@kuatrotech.com>

I would like to thank Yan Gang and Stephane Litkowski for their willingness
to help and efforts over the last 17 months.

Regards,
Alia

--94eb2c1244b64d10cc053a6fbd96
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"font-size:12.8px">In March 2015, I=C2=A0<a h=
ref=3D"https://www.ietf.org/mail-archive/web/routing-discussion/current/msg=
02000.html" target=3D"_blank">created the Routing=C2=A0<span>Yang</span>=C2=
=A0Architecture Design Team and specified a charter</a>.</div><div style=3D=
"font-size:12.8px">The Design Team has done some excellent work helping to =
steer and define the work being done.=C2=A0 This includes=C2=A0<a href=3D"h=
ttps://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/" target=3D"_=
blank">draft-ietf-rtgwg-devi<wbr>ce-model-00</a>,=C2=A0<a href=3D"https://d=
atatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/" target=3D"_blank">draf=
t-ietf-rtgwg-<wbr>lne-model-00</a>, and=C2=A0<a href=3D"https://datatracker=
.ietf.org/doc/draft-ietf-rtgwg-ni-model/" target=3D"_blank">draft-ietf-rtgw=
g-ni-model-<wbr>00</a>=C2=A0as well as identifying issues and work needed t=
o be done in NetMod around improving=C2=A0<span>YANG</span>, such as schema=
 mount and opstate/revised datastores.</div><div style=3D"font-size:12.8px"=
><br></div><div style=3D"font-size:12.8px">At this point, 17 months in, it =
is time to reorganize the=C2=A0<span>DT</span>=C2=A0a bit, set additional g=
oals, say thank you to some members and add some others who are interested.=
</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.=
8px">Going forward, the Design Team will focus on:</div><blockquote style=
=3D"font-size:12.8px;margin:0px 0px 0px 40px;border:none;padding:0px"><div>=
<b>Conventions as specified in the original charter</b>=C2=A0:=C2=A0Common =
conventions and use of=C2=A0<span>YANG</span>=C2=A0=C2=A0 functionality in =
similar ways can help make the interactions of models easier to understand.=
=C2=A0 RFC 6087 provides some guidance; an update is underway now in draft-=
ietf-netmod-rfc6087bis.=C2=A0 If the design team has recommendations for ho=
w the models should be written, those which are not routing-specific can be=
 written down and discussed in netmod.</div><div><br></div></blockquote><bl=
ockquote style=3D"font-size:12.8px;margin:0px 0px 0px 40px;border:none;padd=
ing:0px"><b>Ideas for how to handle extensions and features as specified in=
 the original charter</b>:=C2=A0</blockquote><blockquote style=3D"font-size=
:12.8px;margin:0px 0px 0px 40px;border:none;padding:0px">It is also importa=
nt to consider how future extensibility and features in Routing Area work w=
ill need to be captured in<span>YANG</span>=C2=A0models.=C2=A0 While the IE=
TF is busy developing=C2=A0<span>YANG</span>=C2=A0models, we are still work=
ing on new routing area features and technology.=C2=A0 The design team shou=
ld publish and maintain best current practices for how new features can eas=
ily augment existing=C2=A0<span>YANG</span>=C2=A0models so that authors of =
those new features and technologies can understand how to consider=C2=A0<sp=
an>YANG</span>=C2=A0modeling.<br><br><b>Classification</b>: =C2=A0The abili=
ty to specify metadata for classification and manipulation of models is bei=
ng defined in=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-n=
etmod-yang-model-classification/" target=3D"_blank">draft-ietf-netmod-<span=
>yang</span>-mode<wbr>l-classification-02</a>.=C2=A0 The=C2=A0<span>DT</spa=
n>=C2=A0will suggest classifications for Routing Area=C2=A0<span>YANG</span=
>=C2=A0models and encourage consistency.<br><br><b>Support work based on re=
quirements</b>: =C2=A0The=C2=A0<span>DT</span>=C2=A0will continue to suppor=
t work based on requirements from its previous work.=C2=A0 Examples of such=
 work include=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-n=
etmod-schema-mount/" target=3D"_blank"><br>draft-ietf-netmod-schema-mount<w=
br>-02</a>=C2=A0and opstate/revised datastores.<br><br><b>Progress WG Draft=
s authored</b>: =C2=A0The=C2=A0<span>DT</span>=C2=A0and the specific draft =
authors will push to publication of the existing drafts:=C2=A0<a href=3D"ht=
tps://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/" target=3D"_b=
lank">draft-ietf-rtgwg-devic<wbr>e-model-00</a>,=C2=A0<a href=3D"https://da=
tatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/" target=3D"_blank">draft=
-ietf-rtgwg-<wbr>lne-model-00</a>, and=C2=A0<a href=3D"https://datatracker.=
ietf.org/doc/draft-ietf-rtgwg-ni-model/" target=3D"_blank">draft-ietf-rtgwg=
-ni-model-<wbr>00</a>=C2=A0.<br><br><b>Consistency of Models across the Rou=
ting Area</b>: =C2=A0The=C2=A0<span>DT</span>=C2=A0will look at=C2=A0<span>=
YANG</span>=C2=A0models in the Routing Area and encourage that common parts=
 be factored out into reusable models.=C2=A0 The=C2=A0<span>DT</span>=C2=A0=
will look at how well the set of models will work together and raise any re=
lated issues.=C2=A0 There will be a particular focus on models expected to =
progress to RFC in the next 12 months.<br><br><b>Device Profiles of Needed =
Models:</b>=C2=A0 Different devices will need different sets of=C2=A0<span>=
YANG</span>=C2=A0models for common operations.=C2=A0 There have been some i=
nitial drafts (e.g.=C2=A0<a href=3D"https://www.ietf.org/archive/id/draft-f=
aq-netmod-cpe-yang-profile-00.txt" target=3D"_blank">draft-faq-netmod-cpe-<=
span>yan<wbr>g</span>-profile-00.txt</a>) in this space.=C2=A0 The=C2=A0<sp=
an>DT</span>will provide guidance for what is needed in a device profile, a=
s far as the Routing Area aspects, are concerned and facilitate the creatio=
n of appropriate device profiles.=C2=A0 This should aid in determining what=
 groups of models are needed for practical use for particular device roles.=
<br><br></blockquote><span style=3D"font-size:12.8px">The Design Team membe=
rs will include:</span><div style=3D"font-size:12.8px"><br></div><div style=
=3D"font-size:12.8px"><blockquote style=3D"margin:0px 0px 0px 40px;border:n=
one;padding:0px"><div><span style=3D"color:rgb(0,0,0);font-family:&quot;Tim=
es New Roman&quot;,times,serif;font-size:14.6667px">Lou Berger &lt;</span><=
a href=3D"mailto:lberger@labn.net" style=3D"color:rgb(68,0,136);border-bott=
om-width:0px;font-family:&quot;Times New Roman&quot;,times,serif;font-size:=
14.6667px" target=3D"_blank"><span style=3D"padding-left:14px;background:ur=
l(&quot;http://../envelope.png&quot;) center center no-repeat">=E2=80=8B</s=
pan>lberger@labn.net</a><span style=3D"color:rgb(0,0,0);font-family:&quot;T=
imes New Roman&quot;,times,serif;font-size:14.6667px">&gt; =C2=A0(lead)</sp=
an><br></div><div><span style=3D"color:rgb(0,0,0);font-family:&quot;Times N=
ew Roman&quot;,times,serif;font-size:14.6667px">Acee Lindem &lt;</span><a h=
ref=3D"mailto:acee@cisco.com" style=3D"color:rgb(68,0,136);border-bottom-wi=
dth:0px;font-family:&quot;Times New Roman&quot;,times,serif;font-size:14.66=
67px" target=3D"_blank"><span style=3D"padding-left:14px;background:url(&qu=
ot;http://../envelope.png&quot;) center center no-repeat">=E2=80=8B</span>a=
cee@cisco.com</a><span style=3D"color:rgb(0,0,0);font-family:&quot;Times Ne=
w Roman&quot;,times,serif;font-size:14.6667px">&gt;</span><span style=3D"co=
lor:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times,serif;font-siz=
e:14.6667px"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-fam=
ily:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px">Christian =
Hopps &lt;</span><a href=3D"mailto:chopps@chopps.org" style=3D"color:rgb(68=
,0,136);border-bottom-width:0px;font-family:&quot;Times New Roman&quot;,tim=
es,serif;font-size:14.6667px" target=3D"_blank"><span style=3D"padding-left=
:14px;background:url(&quot;http://../envelope.png&quot;) center center no-r=
epeat">=E2=80=8B</span>chopps@chopps.org</a><span style=3D"color:rgb(0,0,0)=
;font-family:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px">&=
gt;</span><span style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman=
&quot;,times,serif;font-size:14.6667px"><br></span></div><div><span style=
=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times,serif;fo=
nt-size:14.6667px">Dean Bogdanovic &lt;</span><a href=3D"mailto:deanb@junip=
er.net" style=3D"color:rgb(68,0,136);border-bottom-width:0px;font-family:&q=
uot;Times New Roman&quot;,times,serif;font-size:14.6667px" target=3D"_blank=
"><span style=3D"padding-left:14px;background:url(&quot;http://../envelope.=
png&quot;) center center no-repeat">=E2=80=8B</span>deanb@juniper.net</a><s=
pan style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times=
,serif;font-size:14.6667px">&gt;</span><br style=3D"color:rgb(0,0,0);font-f=
amily:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px"></div><d=
iv><span style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,=
times,serif;font-size:14.6667px">Rob Shakir &lt;</span><a href=3D"mailto:rj=
s@rob.sh" style=3D"color:rgb(68,0,136);border-bottom-width:0px;font-family:=
&quot;Times New Roman&quot;,times,serif;font-size:14.6667px" target=3D"_bla=
nk"><span style=3D"padding-left:14px;background:url(&quot;http://../envelop=
e.png&quot;) center center no-repeat">=E2=80=8B</span>rjs@rob.sh</a><span s=
tyle=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times,seri=
f;font-size:14.6667px">&gt;</span><span style=3D"color:rgb(0,0,0);font-fami=
ly:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px"><br></span>=
</div><div><span style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roma=
n&quot;,times,serif;font-size:14.6667px">Anees Shaikh &lt;</span><a href=3D=
"mailto:aashaikh@google.com" style=3D"color:rgb(68,0,136);border-bottom-wid=
th:0px;font-family:&quot;Times New Roman&quot;,times,serif;font-size:14.666=
7px" target=3D"_blank"><span style=3D"padding-left:14px;background:url(&quo=
t;http://../envelope.png&quot;) center center no-repeat">=E2=80=8B</span>aa=
shaikh@google.com</a><span style=3D"color:rgb(0,0,0);font-family:&quot;Time=
s New Roman&quot;,times,serif;font-size:14.6667px">&gt;</span><span style=
=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times,serif;fo=
nt-size:14.6667px"><br></span></div><div><span style=3D"color:rgb(0,0,0);fo=
nt-family:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px">Qin =
Wu &lt;</span><a href=3D"mailto:bill.wu@huawei.com" style=3D"color:rgb(68,0=
,136);border-bottom-width:0px;font-family:&quot;Times New Roman&quot;,times=
,serif;font-size:14.6667px" target=3D"_blank"><span style=3D"padding-left:1=
4px;background:url(&quot;http://../envelope.png&quot;) center center no-rep=
eat">=E2=80=8B</span>bill.wu@huawei.com</a><span style=3D"color:rgb(0,0,0);=
font-family:&quot;Times New Roman&quot;,times,serif;font-size:14.6667px">&g=
t;</span><span style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&=
quot;,times,serif;font-size:14.6667px"><br></span></div><div><div><font col=
or=3D"#000000" face=3D"Times New Roman, times, serif"><span style=3D"font-s=
ize:14.6667px">Ebben Aries =C2=A0&lt;<a href=3D"mailto:exa@juniper.net" tar=
get=3D"_blank">exa@juniper.net</a>&gt;</span></font></div><div><font color=
=3D"#000000" face=3D"Times New Roman, times, serif"><span style=3D"font-siz=
e:14.6667px">Yingzhen Qu &lt;<a href=3D"mailto:yiqu@cisco.com" target=3D"_b=
lank">yiqu@cisco.com</a>&gt;</span></font></div><div><font color=3D"#000000=
" face=3D"Times New Roman, times, serif"><span style=3D"font-size:14.6667px=
">Xufeng Liu=C2=A0</span></font><font color=3D"#000000" face=3D"Times New R=
oman, times, serif" style=3D"font-size:12.8px"><span style=3D"font-size:14.=
6667px">&lt;</span></font><span style=3D"color:rgb(0,0,0);font-family:&quot=
;PT Mono&quot;,Monaco,monospace;font-size:14px;line-height:1.214;background=
-color:rgb(255,253,245)"><a href=3D"mailto:xliu@kuatrotech.com" target=3D"_=
blank">xliu@kuatrotech.com</a></span><span style=3D"font-size:14.6667px;col=
or:rgb(0,0,0);font-family:&quot;Times New Roman&quot;,times,serif">&gt;</sp=
an></div><div style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&q=
uot;,times,serif;font-size:14.6667px"><br></div></div></blockquote><font co=
lor=3D"#000000" face=3D"Times New Roman, times, serif"><span style=3D"font-=
size:14.6667px">I would like to thank Yan Gang and Stephane Litkowski for t=
heir willingness to help and efforts over the last 17 months.</span></font>=
</div><div style=3D"font-size:12.8px"><font color=3D"#000000" face=3D"Times=
 New Roman, times, serif"><span style=3D"font-size:14.6667px"><br></span></=
font></div><div style=3D"font-size:12.8px"><font color=3D"#000000" face=3D"=
Times New Roman, times, serif"><span style=3D"font-size:14.6667px">Regards,=
</span></font></div><div style=3D"font-size:12.8px"><font color=3D"#000000"=
 face=3D"Times New Roman, times, serif"><span style=3D"font-size:14.6667px"=
>Alia</span></font></div></div>

--94eb2c1244b64d10cc053a6fbd96--


From nobody Fri Aug 19 11:21:17 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E94412D9CE; Fri, 19 Aug 2016 11:21:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
Subject: rtgwg - New Meeting Session Request for IETF 97
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147163087662.24274.322047850689778730.idtracker@ietfa.amsl.com>
Date: Fri, 19 Aug 2016 11:21:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/SVhahXYysQofTDSLM-s84NmXw6Q>
Cc: rtgwg@ietf.org, rtgwg-chairs@ietf.org, jeff.tantsura@ericsson.com
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 18:21:16 -0000

A new meeting session request has just been submitted by Jeff Tantsura, a Chair of the rtgwg working group.


---------------------------------------------------------
Working Group Name: Routing Area Working Group
Area Name: Routing Area
Session Requester: Jeff Tantsura

Number of Sessions: 2
Length of Session(s):  2 Hours, 2.5 Hours
Number of Attendees: 150
Conflicts to Avoid: 
 First Priority: isis mpls ospf pce idr spring
 Second Priority: bess l3sm  bier teas ccamp i2rs
 Third Priority: bfd detnet lime nvo3 pim  netmod


Special Requests:
  
---------------------------------------------------------


From nobody Mon Aug 22 06:14:16 2016
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C713412D1EA; Mon, 22 Aug 2016 06:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 CsJCfPoTKmvz; Mon, 22 Aug 2016 06:14:06 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F025B12D50A; Mon, 22 Aug 2016 06:14:05 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0E4F0324634; Mon, 22 Aug 2016 15:14:04 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.63]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id D35E635C079; Mon, 22 Aug 2016 15:14:03 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0301.000; Mon, 22 Aug 2016 15:14:03 +0200
From: <stephane.litkowski@orange.com>
To: "draft-ietf-spring-resiliency-use-cases@ietf.org" <draft-ietf-spring-resiliency-use-cases@ietf.org>
Subject: Shepherd review of draft-oetf-spring-resiliency-use-cases
Thread-Topic: Shepherd review of draft-oetf-spring-resiliency-use-cases
Thread-Index: AdH8dr4WPQceoNkkS8W1oLG3Av5lIw==
Date: Mon, 22 Aug 2016 13:14:03 +0000
Message-ID: <26825_1471871643_57BAFA9B_26825_33_1_9E32478DFA9976438E7A22F69B08FF921BD3D66A@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.17.114517
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/sxzdCaN7TL_QpBqTL47jaM8EVzA>
Cc: "spring@ietf.org" <spring@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 13:14:11 -0000

--_004_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_"


--_000_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I have been selected as Shepherd for this document, and as part of my revie=
w I have several comments that you will find below :

General :
Is it a requirement document ? If yes, it would be good to mention it. The =
document states requirements multiple times.


Abstract :
The abstract is really short, would be good to enhance it with what is exac=
tly described.

In Section 1, there should be an issue with the XML file as the hypertext l=
ink is missing at : "We discuss two different approaches to provide ..., in=
 Section 3". Hyperlink missing for "Section 3".

In Section 2,
It would be good to state in the example that the paths must not be protect=
ed by any local repair techniques. Example : "The two paths are made disjoi=
nt using the SPRING architecture and must not be protected by any local rep=
air techniques".

As a requirement, the two paths must be disjoint (link or node, or srlg), t=
his has some impacts on the path expression : using a node-SID would be a b=
ad idea as there is no guarantee. It would be good to mention that the solu=
tion must take care of this.

It would be easier to state that path T1 is primary and T2 is backup instea=
d of : "When T1 is  up, the packets of the PW are sent on T1".
Why not using the following text :
"T1 is programmed as primary forwarding entry while T2 is a backup entry. I=
n nominal state, PW traffic is carried over T1. When T1 fails, the PW traff=
ic is switched on T2".
Before telling that the solution for end-to-end liveness is out of scope, i=
t would be good to state that it is mandatory to have such mechanism to mak=
e the solution work. Is it a SPRING path liveness check or service liveness=
 check ?  It would be good to tell who is in charge of the detection and pa=
th switchover ? is it LSP ingress, is it a node outside SPRING network ? If=
 there are multiple options, please tell it.

I would propose to change the last sentence to highlight the two requiremen=
ts in case we need SPRING path liveness check :
"From a SPRING viewpoint, the SPRING architecture MUST provide end-to-end l=
iveness check of SPRING based LSPs. In addition, it MUST provide a way to c=
reate LSPs that must not be protected by local repair techniques."

Globally this section looks confusing to me. End to end protection could be=
 achieved in multiple ways, for example :
- Having a dumb network that only provides disjoint non protected path and =
having end-to-end probes at service level that would help an external compo=
nent to switchover traffic. Provider network is not aware of the protection=
 done. In your figure we can add A' and Z', and we establish two disjoint L=
SPs (A->Z and A'->Z'). Customer is dual meshed to A/A' and Z/Z' and is mana=
ging liveness check and switchover (network is not involved).
- Having primary/backup like approach : two disjoint LSPs from A->Z , A pro=
grams one in FIB. A provides OAM on the LSP. When primary LSP fails, the se=
cond one is installed in FIB.
- Having FRR like approach : two disjoint LSPs from A->Z , A programs both =
in FIB in a FRR like fashion. A provides aggressive OAM on the LSPs to enab=
le traffic switchover in a very short time.

The current text is not really clear on the proposed approach. Maybe anothe=
r one ?


Section 3
s/the backup path computation should/the backup path computation SHOULD/
s/in any topology/in any topology./
s/by the IGP/by the IGP./

Section 3.1
"ending at the protected nexthop", that's true only for link protection, bu=
t not possible in case of node protection. This sentence is a generic one a=
nd is not specific to link protection case.
I cannot parse : "so as to bypass the failed component ..."
I would propose something like :
"One way to provide local repair is to enforce a failover along the shortes=
t path around the protected component. In case of link protection,  the poi=
nt of local repair will create a bypass avoiding the protected link and mer=
ging back to primary path at the nexthop. In case of node protection, the b=
ypass will avoid the protected node and merge back to primary path at the n=
ext-nexthop."
What about SRLG case ?

"In our example, C protects Z", protects for what ? link / node /srlg failu=
re ? proposed text : "In our example, C protects destination Z for a failur=
e CD link"

"that it initially reaches via CD", yes and also using CH because of ECMP, =
it would be better to change the example to disable ECMP. There are multipl=
e ECMPs that would not help the reading. Even A as ECMP to Z.


Section 3.2
"providing a repair for the destination based on shortest path state for th=
at destination". Why using "state" ?
Again : "In our example, C protects Z", protects for what ? link / node /sr=
lg failure ?

You have again ECMP starting from A, and at other nodes that complexifies t=
he example.

Why not talking about pros/cons between approaches ?


Section 4.
SRLG was mentioned as a requirement in Section 3. So why considering it as =
a more high level constraint ?
If SRLG is management-free, please change your example with another constra=
int type (bandwidth for example).
You can refer to RFC7916 as an example of managed computation. Similar appr=
oach can be used here.

Section 4.1
Is the path {CG,GH,HD} computed automatically or putted manually ? Please b=
e clear on what must be done.

Section 4.2
This case is a bit strange. The goal is to use shortest path protection to =
the destination but here we enforce a non shortest path, so the name is no =
more applicable. It is more a per-destination protection tweaking. Again ho=
w is it done, configured manually per destination or group of destinations =
? Do you have requirements here ?

Section 5
First sentence is hard to read (it works but hard to read). Is it possible =
to make it simpler ? For example, "when a topology change occurs in a netwo=
rk, transient inconsistencies of router FIBs can occur."
Could you point to relevant RFCs/drafts on microloops to help readers that =
are interested by more information on the subject.

You could tell that those micro-loops are breaking local repair techniques =
preventing 50msec restoration.

Could you provide an example on how SPRING can prevent loops ? (as you done=
 for protection cases)

Section 6.
Could you rename the title to be more explicit : co-existence of what ?

Section 8.
You also provide requirements, and you have example of manageability requir=
ements (revert ability for path protection, managed path) ...
Please state clearly that the manageability requirements provided in this d=
ocument must be addressed by the solution documents. Could you summarize th=
e manageability requirements here ?



Best Regards,

Stephane








[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


--_000_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have been selected as Shepherd for this document, =
and as part of my review I have several comments that you will find below :=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General :<o:p></o:p></p>
<p class=3D"MsoNormal">Is it a requirement document ? If yes, it would be g=
ood to mention it. The document states requirements multiple times.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Abstract :<o:p></o:p></p>
<p class=3D"MsoNormal">The abstract is really short, would be good to enhan=
ce it with what is exactly described.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In Section 1, there should be an issue with the XML =
file as the hypertext link is missing at : &#8220;We discuss two different =
approaches to provide &#8230;, in Section 3&#8221;. Hyperlink missing for &=
#8220;Section 3&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In Section 2, <o:p></o:p></p>
<p class=3D"MsoNormal">It would be good to state in the example that the pa=
ths must not be protected by any local repair techniques. Example : &#8220;=
The two paths are made disjoint using the SPRING architecture and must not =
be protected by any local repair techniques&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As a requirement, the two paths must be disjoint (li=
nk or node, or srlg), this has some impacts on the path expression : using =
a node-SID would be a bad idea as there is no guarantee. It would be good t=
o mention that the solution must take
 care of this.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It would be easier to state that path T1 is primary =
and T2 is backup instead of : &#8220;When T1 is&nbsp; up, the packets of th=
e PW are sent on T1&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal">Why not using the following text :<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;T1 is programmed as primary forwarding entry =
while T2 is a backup entry. In nominal state, PW traffic is carried over T1=
. When T1 fails, the PW traffic is switched on T2&#8221;.
<o:p></o:p></p>
<p class=3D"MsoNormal">Before telling that the solution for end-to-end live=
ness is out of scope, it would be good to state that it is mandatory to hav=
e such mechanism to make the solution work. Is it a SPRING path liveness ch=
eck or service liveness check ?&nbsp; It
 would be good to tell who is in charge of the detection and path switchove=
r ? is it LSP ingress, is it a node outside SPRING network ? If there are m=
ultiple options, please tell it.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would propose to change the last sentence to highl=
ight the two requirements in case we need SPRING path liveness check :<o:p>=
</o:p></p>
<p class=3D"MsoNormal">&#8220;From a SPRING viewpoint, the SPRING architect=
ure MUST provide end-to-end liveness check of SPRING based LSPs. In additio=
n, it MUST provide a way to create LSPs that must not be protected by local=
 repair techniques.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Globally this section looks confusing to me. End to =
end protection could be achieved in multiple ways, for example :<o:p></o:p>=
</p>
<p class=3D"MsoNormal">- Having a dumb network that only provides disjoint =
non protected path and having end-to-end probes at service level that would=
 help an external component to switchover traffic. Provider network is not =
aware of the protection done. In your
 figure we can add A&#8217; and Z&#8217;, and we establish two disjoint LSP=
s (A-&gt;Z and A&#8217;-&gt;Z&#8217;). Customer is dual meshed to A/A&#8217=
; and Z/Z&#8217; and is managing liveness check and switchover (network is =
not involved).<o:p></o:p></p>
<p class=3D"MsoNormal">- Having primary/backup like approach : two disjoint=
 LSPs from A-&gt;Z , A programs one in FIB. A provides OAM on the LSP. When=
 primary LSP fails, the second one is installed in FIB.<o:p></o:p></p>
<p class=3D"MsoNormal">- Having FRR like approach : two disjoint LSPs from =
A-&gt;Z , A programs both in FIB in a FRR like fashion. A provides aggressi=
ve OAM on the LSPs to enable traffic switchover in a very short time.<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The current text is not really clear on the proposed=
 approach. Maybe another one ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 3<o:p></o:p></p>
<p class=3D"MsoNormal">s/the backup path computation should/the backup path=
 computation SHOULD/<o:p></o:p></p>
<p class=3D"MsoNormal">s/in any topology/in any topology./<o:p></o:p></p>
<p class=3D"MsoNormal">s/by the IGP/by the IGP./<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 3.1<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;ending at the protected nexthop&#8221;, that&=
#8217;s true only for link protection, but not possible in case of node pro=
tection. This sentence is a generic one and is not specific to link protect=
ion case.<o:p></o:p></p>
<p class=3D"MsoNormal">I cannot parse : &#8220;so as to bypass the failed c=
omponent &#8230;&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">I would propose something like :<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;One way to provide local repair is to enforce=
 a failover along the shortest path around the protected component. In case=
 of link protection,&nbsp; the point of local repair will create a bypass a=
voiding the protected link and merging back to
 primary path at the nexthop. In case of node protection, the bypass will a=
void the protected node and merge back to primary path at the next-nexthop.=
&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">What about SRLG case ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;In our example, C protects Z&#8221;, protects=
 for what ? link / node /srlg failure ? proposed text : &#8220;In our examp=
le, C protects destination Z for a failure CD link&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;<span style=3D"color:black">that it initially=
 reaches via CD&#8221;, yes and also using CH because of ECMP, it would be =
better to change the example to disable ECMP. There are multiple ECMPs that=
 would not help the reading. Even A as ECMP to Z.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Section 3.2<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;providing a repai=
r for the destination based on shortest path state for that destination&#82=
21;. Why using &#8220;state&#8221; ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Again : </span>&#8220;In=
 our example, C protects Z&#8221;, protects for what ? link / node /srlg fa=
ilure ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">You have again ECMP starting from A, and at other no=
des that complexifies the example.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Why not talking about pros/cons between approaches ?=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.<o:p></o:p></p>
<p class=3D"MsoNormal">SRLG was mentioned as a requirement in Section 3. So=
 why considering it as a more high level constraint ?<o:p></o:p></p>
<p class=3D"MsoNormal">If SRLG is management-free, please change your examp=
le with another constraint type (bandwidth for example).<o:p></o:p></p>
<p class=3D"MsoNormal">You can refer to RFC7916 as an example of managed co=
mputation. Similar approach can be used here.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.1<o:p></o:p></p>
<p class=3D"MsoNormal">Is the path {CG,GH,HD} computed automatically or put=
ted manually ? Please be clear on what must be done.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.2<o:p></o:p></p>
<p class=3D"MsoNormal">This case is a bit strange. The goal is to use short=
est path protection to the destination but here we enforce a non shortest p=
ath, so the name is no more applicable. It is more a per-destination protec=
tion tweaking. Again how is it done,
 configured manually per destination or group of destinations ? Do you have=
 requirements here ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5<o:p></o:p></p>
<p class=3D"MsoNormal">First sentence is hard to read (it works but hard to=
 read). Is it possible to make it simpler ? For example, &#8220;when a topo=
logy change occurs in a network, transient inconsistencies of router FIBs c=
an occur.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">Could you point to relevant RFCs/drafts on microloop=
s to help readers that are interested by more information on the subject.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">You could tell that those micro-loops are breaking l=
ocal repair techniques preventing 50msec restoration.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Could you provide an example on how SPRING can preve=
nt loops ? (as you done for protection cases)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6.<o:p></o:p></p>
<p class=3D"MsoNormal">Could you rename the title to be more explicit : co-=
existence of what ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.<o:p></o:p></p>
<p class=3D"MsoNormal">You also provide requirements, and you have example =
of manageability requirements (revert ability for path protection, managed =
path) &#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">Please state clearly that the manageability requirem=
ents provided in this document must be addressed by the solution documents.=
 Could you summarize the manageability requirements here ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Best Regards,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Stephane<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;co=
lor:blue;text-decoration:none"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.jpg@01D1FC78.CCED64C0" alt=3D"O=
range logo"></span></a><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Future Networks=
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:black">phone:
</span><a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhtt=
p%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Factio=
n%3Ddefault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%208=
3%20"><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&q=
uot;,&quot;sans-serif&quot;;color:black">&#43;33
 2 23 28 49 83 </span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
</span><a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhtt=
p%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Factio=
n%3Ddefault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%205=
2%20"><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&q=
uot;,&quot;sans-serif&quot;;color:black">&#43;33
 6 37 86 97 52 </span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"><br>
</span><a href=3D"mailto:stephane.litkowski@orange.com"><span lang=3D"FR" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:#FF6600">stephane.litkowski@orange.com</span></a><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">
<span lang=3D"FR"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_--

--_004_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Mon, 22 Aug 2016 13:14:02 GMT";
	modification-date="Mon, 22 Aug 2016 13:14:02 GMT"
Content-ID: <image001.jpg@01D1FC78.CCED64C0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_9E32478DFA9976438E7A22F69B08FF921BD3D66AOPEXCLILMA4corp_--


From nobody Fri Aug 26 11:13:09 2016
Return-Path: <kwatsen@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC1C12D603 for <rtgwg@ietfa.amsl.com>; Fri, 26 Aug 2016 11:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 8vT266NxaCHm for <rtgwg@ietfa.amsl.com>; Fri, 26 Aug 2016 11:13:06 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0102.outbound.protection.outlook.com [104.47.33.102]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4D7212D18D for <rtgwg@ietf.org>; Fri, 26 Aug 2016 11:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ob1frCoJbv1onPjBt+XiOZL91/V9OVTCWxnh+0oJSlI=; b=j0WdI5iKUHcvL4qiSDpoLcGU98udkOy0k46ntdUu/tBN+WbAOGm+0wbWLck32yG8luVR+1BfD5CNvec/oSW5XEwB7sNK2dzxNKFV/bAIA7LI+zGzkOO771FncxzuI9Mnyhn3lPW8oWoQEAh+tYc4XUv/fNmfbb01y1419pG6CfQ=
Received: from DM2PR0501MB1455.namprd05.prod.outlook.com (10.161.224.152) by DM2PR0501MB1456.namprd05.prod.outlook.com (10.161.224.153) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.2; Fri, 26 Aug 2016 18:13:02 +0000
Received: from DM2PR0501MB1455.namprd05.prod.outlook.com ([10.161.224.152]) by DM2PR0501MB1455.namprd05.prod.outlook.com ([10.161.224.152]) with mapi id 15.01.0599.001; Fri, 26 Aug 2016 18:13:02 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: [netmod] WG Last Call for draft-ietf-netmod-routing-cfg-23 (until Sep 9, 2016)
Thread-Topic: [netmod] WG Last Call for draft-ietf-netmod-routing-cfg-23 (until  Sep 9, 2016)
Thread-Index: AQHR/8V7i+UQoOx0+kWx2PlZyzBk/Q==
Date: Fri, 26 Aug 2016 18:13:02 +0000
Message-ID: <3F424C84-67EC-44F2-8BD3-24CD3A083733@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kwatsen@juniper.net; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.11]
x-ms-office365-filtering-correlation-id: dbe89217-2b85-448e-2dca-08d3cddc9e9b
x-microsoft-exchange-diagnostics: 1; DM2PR0501MB1456; 6:tvWb+FhvZJngTZMFsjkXWD8tDrXS4fvggO7rlpRpiCDxgV0oJry3x6u57aQ0sRs75Pfu2WSeooP9Y7Ct7D56IbRltarh7vRGbhPERZyHr0kYk0n2looi+SREG7HMU5m9O7WnENxv+qTEMC050pMuO5Or3WyWP4Him42My88wx7rsl78AxZEutXrILgeUx9NVAHUeycsmnFrZnhTDoiaBFaRHoLH1wtys9MC6xou0G+XC+4kCJKqyZOZ/8rahdmCOGBNY3HUIXLkVazLqEfaU/uwBMSnjg8F8BXY4hZEDHH+A0jIE2ZYjP1SHzirgeJOLgWuViFQwvNprercVt0XOEw==; 5:KF9Yjv4YzWKJ6qlNuxB9bYwmZh6j5QGhbxxeS99dKzNr49baSYVCLEMVuEOtXpdZOvs6tJS48SxfjbvlwTGzk4ejA9YLC7HjtF2Jon3Da4b2xKbh0fL73Uc7MP9+oG7LRtxKft2kU/RJIaJ/l0geHQ==; 24:ncP2XAJJD7LHx0PNR61f8gqGFon5JQ+ipZkmF9Ww60kQ/pm597wLak8i0STbPkmkdAkzv1X8KPM3HNF3YeI1Rz+VwIn7iJhyKoGR/6Cb0VE=; 7:YAEDoC3SBED2/SjUJiXJTLL6iEPW0p2IEg7Xp4u+vB4i5aikkwkhzM/qnLojpEXtdIEDLNcoiOnHOnZVpwCCdLmvLyRvoZ7xzSW5M/4VQXWzSIVyklzosn7fQmXkun+YjZjFPIlAt6Dh6MMR/zC4VCClo29eyQqgpq1UrufP+0ZqU5ejXJ4vbUU8SVFVNKVSx3/5tnpUZucX+1+AxIBee9HZiYe9JHyS+/HbON9CzeIwEKRTgI1Ah4H5bIlmugQe
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0501MB1456;
x-microsoft-antispam-prvs: <DM2PR0501MB1456EA0B8B58ECF8CC5F06ABA5EC0@DM2PR0501MB1456.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506)(138986009662008)(21748063052155); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415321)(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:DM2PR0501MB1456; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1456; 
x-forefront-prvs: 00462943DE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(377454003)(189002)(199003)(69234005)(83506001)(86362001)(3846002)(1730700003)(81156014)(3280700002)(8676002)(3660700001)(6116002)(2501003)(102836003)(8936002)(106116001)(230783001)(5002640100001)(450100001)(36756003)(19625215002)(77096005)(87936001)(19580405001)(19300405004)(99936001)(54356999)(15975445007)(5640700001)(99286002)(33656002)(2906002)(101416001)(66066001)(105586002)(50986999)(19580395003)(11100500001)(7846002)(110136002)(68736007)(2351001)(189998001)(92566002)(83716003)(81166006)(586003)(107886002)(97736004)(4001350100001)(2900100001)(106356001)(7736002)(10400500002)(122556002)(5660300001)(16236675004)(82746002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1456; H:DM2PR0501MB1455.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_004_3F424C8467EC44F28BD324CD3A083733junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2016 18:13:02.5049 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1456
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/KBKPK-_Z2k5yrK9WXkdoY81VzRc>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 18:13:08 -0000

--_004_3F424C8467EC44F28BD324CD3A083733junipernet_
Content-Type: multipart/alternative;
	boundary="_000_3F424C8467EC44F28BD324CD3A083733junipernet_"

--_000_3F424C8467EC44F28BD324CD3A083733junipernet_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RllJLCBidXQgcGxlYXNlIHNlbmQgYW55IHJlc3BvbnNlcyB0byB0aGUgTkVUTU9EIFdHIGxpc3Qu
DQoNCktlbnQgIC8vIE5FVE1PRCBjby1jaGFpcg0KDQpGcm9tOiBuZXRtb2QgPG5ldG1vZC1ib3Vu
Y2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2YgS2VudCBXYXRzZW4gPGt3YXRzZW5AanVuaXBlci5u
ZXQ+DQpEYXRlOiBGcmlkYXksIEF1Z3VzdCAyNiwgMjAxNiBhdCAxOjU0IFBNDQpUbzogIm5ldG1v
ZEBpZXRmLm9yZyIgPG5ldG1vZEBpZXRmLm9yZz4NClN1YmplY3Q6IFtuZXRtb2RdIFdHIExhc3Qg
Q2FsbCBmb3IgZHJhZnQtaWV0Zi1uZXRtb2Qtcm91dGluZy1jZmctMjMgKHVudGlsIFNlcCA5LCAy
MDE2KQ0KDQoNClRoaXMgaXMgYSBub3RpY2UgdG8gc3RhcnQgYSB0d28td2VlayBORVRNT0QgV0cg
bGFzdCBjYWxsIGZvciB0aGUgZG9jdW1lbnQ6DQoNCiAgICAgICAgICAgICAgICBBIFlBTkcgRGF0
YSBNb2RlbCBmb3IgUm91dGluZyBNYW5hZ2VtZW50DQogICAgICAgICAgICAgICAgaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0bW9kLXJvdXRpbmctY2ZnLTIzDQoNClBs
ZWFzZSBpbmRpY2F0ZSB5b3VyIHN1cHBvcnQgb3IgY29uY2VybnMgYnkgVGh1cnNkYXkgU2VwdGVt
YmVyIDksIDIwMTYuDQoNCldlIGFyZSBub3Qgb25seSBpbnRlcmVzdGVkIGluIHJlY2VpdmluZyBk
ZWZlY3QgcmVwb3J0cywgd2UgYXJlIGVxdWFsbHkgaW50ZXJlc3RlZCBpbiBzdGF0ZW1lbnRzIG9m
IHRoZSBmb3JtOg0KDQogICogSSBoYXZlIHJldmlld2VkIGRyYWZ0LWlldGYtbmV0bW9kLXJvdXRp
bmctY2ZnLTIzIGFuZCBJIGZvdW5kIG5vIGlzc3Vlcw0KICAqIEkgaGF2ZSBpbXBsZW1lbnRlZCB0
aGUgZGF0YSBtb2RlbCBpbiBkcmFmdC1pZXRmLW5ldG1vZC1yb3V0aW5nLWNmZy0yMw0KICAqIEkg
YW0gaW1wbGVtZW50aW5nIHRoZSBkYXRhIG1vZGVsIGluIGRyYWZ0LWlldGYtbmV0bW9kLXJvdXRp
bmctY2ZnLTIzDQogICogSSBhbSBjb25zaWRlcmluZyB0byBpbXBsZW1lbnQgdGhlIGRhdGEgbW9k
ZWwgaW4gZHJhZnQtaWV0Zi1uZXRtb2Qtcm91dGluZy1jZmctMjMNCg0KT2YgY291cnNlLCB0aGVz
ZSBhcmUgbWVyZWx5IHN1Z2dlc3Rpb25zLCBmb2xrcyBjYW4gcHJvdmlkZSBjb21tZW50cyBpbiBh
bnkgZm9ybSB0aGF0IHN1aXRzIHRoZW0uDQoNCg0KVGhhbmsgeW91LA0KDQpORVRNT0QgV0cgQ2hh
aXJzDQoNCg0K

--_000_3F424C8467EC44F28BD324CD3A083733junipernet_
Content-Type: text/html; charset="utf-8"
Content-ID: <5D80CB7EDE62A94890B397593BB30624@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eTpDYWxpYnJpO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1z
b1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OkNhbGlicmk7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1l
OiJQbGFpbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiUGxhaW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTt9DQpzcGFuLkVtYWlsU3R5
bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseTpDYWxpYnJpOw0K
CWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCnNwYW4ubXNvSW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCW1zby1zdHls
ZS1uYW1lOiIiOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJY29sb3I6dGVhbDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJn
aW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUi
IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNz
PSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPkZZSSwgYnV0IHBsZWFzZSBzZW5kIGFueSByZXNwb25zZXMgdG8gdGhlIE5F
VE1PRCBXRyBsaXN0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+
S2VudCZuYnNwOyAvLyBORVRNT0QgY28tY2hhaXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5Gcm9tOiA8L3NwYW4+PC9i
PjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+bmV0bW9kICZsdDtuZXRtb2QtYm91bmNlc0BpZXRm
Lm9yZyZndDsgb24gYmVoYWxmIG9mIEtlbnQgV2F0c2VuICZsdDtrd2F0c2VuQGp1bmlwZXIubmV0
Jmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5GcmlkYXksIEF1Z3VzdCAyNiwgMjAxNiBhdCAxOjU0IFBN
PGJyPg0KPGI+VG86IDwvYj4mcXVvdDtuZXRtb2RAaWV0Zi5vcmcmcXVvdDsgJmx0O25ldG1vZEBp
ZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+W25ldG1vZF0gV0cgTGFzdCBDYWxsIGZv
ciBkcmFmdC1pZXRmLW5ldG1vZC1yb3V0aW5nLWNmZy0yMyAodW50aWwgU2VwIDksIDIwMTYpPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdCI+VGhpcyBpcyBhIG5vdGljZSB0byBzdGFydCBhIHR3by13ZWVrIE5FVE1PRCBX
RyBsYXN0IGNhbGwgZm9yIHRoZSBkb2N1bWVudDo8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7PC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBBIFlBTkcg
RGF0YSBNb2RlbCBmb3IgUm91dGluZyBNYW5hZ2VtZW50PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1uZXRtb2Qtcm91dGluZy1jZmctMjM8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQiPlBsZWFzZSBpbmRpY2F0ZSB5b3VyIHN1cHBvcnQgb3IgY29uY2Vy
bnMgYnkgVGh1cnNkYXkgU2VwdGVtYmVyIDksIDIwMTYuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNw
Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij5XZSBhcmUgbm90IG9ubHkgaW50ZXJlc3RlZCBpbiByZWNlaXZp
bmcgZGVmZWN0IHJlcG9ydHMsIHdlIGFyZSBlcXVhbGx5IGludGVyZXN0ZWQgaW4gc3RhdGVtZW50
cyBvZiB0aGUgZm9ybTo8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQi
PiZuYnNwOyAqIEkgaGF2ZSByZXZpZXdlZCBkcmFmdC1pZXRmLW5ldG1vZC1yb3V0aW5nLWNmZy0y
MyBhbmQgSSBmb3VuZCBubyBpc3N1ZXM8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7ICogSSBoYXZl
IGltcGxlbWVudGVkIHRoZSBkYXRhIG1vZGVsIGluIGRyYWZ0LWlldGYtbmV0bW9kLXJvdXRpbmct
Y2ZnLTIzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNwOyAqIEkgYW0gaW1wbGVtZW50aW5nIHRoZSBk
YXRhIG1vZGVsIGluIGRyYWZ0LWlldGYtbmV0bW9kLXJvdXRpbmctY2ZnLTIzPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPiZuYnNwOyAqIEkgYW0gY29uc2lkZXJpbmcgdG8gaW1wbGVtZW50IHRoZSBkYXRhIG1v
ZGVsIGluIGRyYWZ0LWlldGYtbmV0bW9kLXJvdXRpbmctY2ZnLTIzPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQi
PiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5PZiBjb3Vyc2UsIHRoZXNlIGFyZSBtZXJlbHkgc3Vn
Z2VzdGlvbnMsIGZvbGtzIGNhbiBwcm92aWRlIGNvbW1lbnRzIGluIGFueSBmb3JtIHRoYXQgc3Vp
dHMgdGhlbS48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+VGhhbmsgeW91LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+TkVUTU9EIFdHIENoYWlyczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_3F424C8467EC44F28BD324CD3A083733junipernet_--

--_004_3F424C8467EC44F28BD324CD3A083733junipernet_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=133;
	creation-date="Fri, 26 Aug 2016 18:13:01 GMT";
	modification-date="Fri, 26 Aug 2016 18:13:01 GMT"
Content-ID: <4E8BAC6D4948FA48B56D3744439F09A8@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm5ldG1vZCBt
YWlsaW5nIGxpc3QNCm5ldG1vZEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9uZXRtb2QNCg==

--_004_3F424C8467EC44F28BD324CD3A083733junipernet_--


From nobody Fri Aug 26 12:35:59 2016
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6CD12D7B4; Fri, 26 Aug 2016 12:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.068
X-Spam-Level: 
X-Spam-Status: No, score=-15.068 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 KBvRc8Hmbj_U; Fri, 26 Aug 2016 12:35:54 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E44012D7CD; Fri, 26 Aug 2016 12:35:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11973; q=dns/txt; s=iport; t=1472240154; x=1473449754; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5i3TmuzEy0mn8TQa5SR37kFsYA3GgEyXdxRvwMRomJw=; b=LnzxeDJk/Ldq0pawfk5hq3tisf0P5fIhKd4htDNvDv5N+rORs13lwXuc 1CLHDxTzbJ2yhfy5EBPOiKFMkRSzbi+oxKbJfaLfbhNimL1yZwjJXLFR1 HXGdc1Pu/clJKQc3LgFcs+MzB8vE8t7IlFlG6mZh1qlzBT4DpNL48QOYm c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAgC2mcBX/5hdJa1dGgEBAQGCcDMBA?= =?us-ascii?q?QEBAR5WfAeNKKVvhQmCASSFeQIcgTQ4FAEBAQEBAQEBAQFeJ4RhAQEBBCNRBRA?= =?us-ascii?q?CAQgOAwMBAigDAgICMBQJCAIEAQ0FiDgOsA6PNQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARyKe4QSEQEzCYJigloFmUwBhh+JCYFtToQPiQiMQ4N4AQ8PNoQccAGELIE?= =?us-ascii?q?gfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.28,582,1464652800";  d="scan'208,217";a="315718325"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2016 19:35:53 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7QJZqpg015104 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Aug 2016 19:35:53 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 26 Aug 2016 15:35:52 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 26 Aug 2016 15:35:52 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Kent Watsen <kwatsen@juniper.net>, Ladislav Lhotka <lhotka@nic.cz>
Subject: Re: Regarding IPR on draft-ietf-netmod-routing-cfg-23
Thread-Topic: Regarding IPR on draft-ietf-netmod-routing-cfg-23
Thread-Index: AQHR/8NtBYbihfSd2UO+EQ0BQo+j6KBbopAA
Date: Fri, 26 Aug 2016 19:35:51 +0000
Message-ID: <D3E61222.7B6E6%acee@cisco.com>
References: <5E95D548-556B-481F-BC97-4C7E2FB876CF@juniper.net>
In-Reply-To: <5E95D548-556B-481F-BC97-4C7E2FB876CF@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D3E612227B6E6aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/vK2D_tUo8yfiZdUkDvBUAr9wCpw>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 19:35:57 -0000

--_000_D3E612227B6E6aceeciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

U3BlYWtlciBhcyBhbiBhdXRob3IsDQoNCk5vLCBJIGFtIG5vdCBhd2FyZSBvZiBhbiBJUFIgdGhh
dCBhcHBsaWVzIHRvIHRoaXMgZHJhZnQuDQoNClRoYW5rcywNCkFjZWUNCg0KRnJvbTogS2VudCBX
YXRzZW4gPGt3YXRzZW5AanVuaXBlci5uZXQ8bWFpbHRvOmt3YXRzZW5AanVuaXBlci5uZXQ+Pg0K
RGF0ZTogRnJpZGF5LCBBdWd1c3QgMjYsIDIwMTYgYXQgMTo1OCBQTQ0KVG86IExhZGlzbGF2IExo
b3RrYSA8bGhvdGthQG5pYy5jejxtYWlsdG86bGhvdGthQG5pYy5jej4+LCBBY2VlIExpbmRlbSA8
YWNlZUBjaXNjby5jb208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4NCkNjOiAibmV0bW9kQGlldGYu
b3JnPG1haWx0bzpuZXRtb2RAaWV0Zi5vcmc+IiA8bmV0bW9kQGlldGYub3JnPG1haWx0bzpuZXRt
b2RAaWV0Zi5vcmc+PiwgIm5ldG1vZC1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOm5ldG1vZC1jaGFp
cnNAaWV0Zi5vcmc+IiA8bmV0bW9kLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86bmV0bW9kLWNoYWly
c0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZWdhcmRpbmcgSVBSIG9uIGRyYWZ0LWlldGYtbmV0bW9k
LXJvdXRpbmctY2ZnLTIzDQoNCg0KQXV0aG9ycywgQ29udHJpYnV0b3JzLCBXRywNCg0KDQoNCkFz
IHBhcnQgb2YgdGhlIFdHIExhc3QgQ2FsbCwgYXJlIHlvdSBhd2FyZSBvZiBhbnkgSVBSIHRoYXQg
YXBwbGllcyB0byBkcmFmdCBpZGVudGlmaWVkIGFib3ZlPyAgUGxlYXNlIHN0YXRlIGVpdGhlcjoN
Cg0KICAqICJObywgSSdtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIHRoYXQgYXBwbGllcyB0byB0aGlz
IGRyYWZ0Ig0KDQogICogIlllcywgSSdtIGF3YXJlIG9mIElQUiB0aGF0IGFwcGxpZXMgdG8gdGhp
cyBkcmFmdCINCg0KDQoNCklmIOKAnHllc+KAnSwgaGFzIHRoaXMgSVBSIGJlZW4gZGlzY2xvc2Vk
IGluIGNvbXBsaWFuY2Ugd2l0aCBJRVRGIElQUiBydWxlcyAoc2VlIFJGQ3MgMzk3OSwgNDg3OSwg
MzY2OSBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzKT8gICBQbGVhc2Ugc3RhdGUgZWl0aGVyOg0K
DQogICogIlllcywgdGhlIElQUiBoYXMgYmVlbiBkaXNjbG9zZWQgaW4gY29tcGxpYW5jZSB3aXRo
IElFVEYgSVBSIHJ1bGVzIg0KDQogICogIk5vLCB0aGUgSVBSIGhhcyBub3QgYmVlbiBkaXNjbG9z
ZWQiDQoNCg0KDQpJZiB5b3UgYW5zd2VyIOKAnG5v4oCdLCBwbGVhc2UgcHJvdmlkZSBhbnkgYWRk
aXRpb25hbCBkZXRhaWxzIHlvdSB0aGluayBhcHByb3ByaWF0ZS4NCg0KDQoNCklmIHlvdSBhcmUg
bGlzdGVkIGFzIGEgZG9jdW1lbnQgYXV0aG9yIG9yIGNvbnRyaWJ1dG9yLCBwbGVhc2UgYW5zd2Vy
IHRoZSBhYm92ZSBieSByZXNwb25kaW5nIHRvIHRoaXMgZW1haWwgcmVnYXJkbGVzcyBvZiB3aGV0
aGVyIG9yIG5vdCB5b3UgYXJlIGF3YXJlIG9mIGFueSByZWxldmFudCBJUFIuIFRoaXMgZG9jdW1l
bnQgd2lsbCBub3QgYWR2YW5jZSB0byB0aGUgbmV4dCBzdGFnZSB1bnRpbCBhIHJlc3BvbnNlIGhh
cyBiZWVuIHJlY2VpdmVkIGZyb20gZWFjaCBhdXRob3IgYW5kIGxpc3RlZCBjb250cmlidXRvci4g
Tk9URTogVEhJUyBBUFBMSUVTIFRPIEFMTCBPRiBZT1UgTElTVEVEIElOIFRISVMgTUVTU0FHRSdT
IFRPIExJTkVTLg0KDQoNCg0KSWYgeW91IGFyZSBvbiB0aGUgV0cgZW1haWwgbGlzdCBvciBhdHRl
bmQgV0cgbWVldGluZ3MgYnV0IGFyZSBub3QgbGlzdGVkIGFzIGFuIGF1dGhvciBvciBjb250cmli
dXRvciwgd2UgcmVtaW5kIHlvdSBvZiB5b3VyIG9ibGlnYXRpb25zIHVuZGVyIHRoZSBJRVRGIElQ
UiBydWxlcyB3aGljaCBlbmNvdXJhZ2VzIHlvdSB0byBub3RpZnkgdGhlIElFVEYgaWYgeW91IGFy
ZSBhd2FyZSBvZiBJUFIgb2Ygb3RoZXJzIG9uIGFuIElFVEYgY29udHJpYnV0aW9uLCBvciB0byBy
ZWZyYWluIGZyb20gcGFydGljaXBhdGluZyBpbiBhbnkgY29udHJpYnV0aW9uIG9yIGRpc2N1c3Np
b24gcmVsYXRlZCB0byB5b3VyIHVuZGlzY2xvc2VkIElQUi4gRm9yIG1vcmUgaW5mb3JtYXRpb24s
IHBsZWFzZSBzZWUgdGhlIFJGQ3MgbGlzdGVkIGFib3ZlIGFuZCBodHRwOi8vdHJhYy50b29scy5p
ZXRmLm9yZy9ncm91cC9pZXNnL3RyYWMvd2lraS9JbnRlbGxlY3R1YWxQcm9wZXJ0eS4NCg0KDQoN
ClBTOiBQbGVhc2UgaW5jbHVkZSBhbGwgbGlzdGVkIGluIHRoZSBoZWFkZXJzIG9mIHRoaXMgbWVz
c2FnZSBpbiB5b3VyIHJlc3BvbnNlLg0KDQoNCg0KVGhhbmsgeW91LA0KDQpORVRNT0QgV0cgQ2hh
aXJzDQoNCg0KDQoNCg0KDQo=

--_000_D3E612227B6E6aceeciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <BDFB7C4F0914CF4295F58FB33AB4A3BD@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5TcGVha2VyIGFz
IGFuIGF1dGhvciw8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk5vLCBJIGFtIG5vdCBh
d2FyZSBvZiBhbiBJUFIgdGhhdCBhcHBsaWVzIHRvIHRoaXMgZHJhZnQuJm5ic3A7PC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGFua3MsPC9kaXY+DQo8ZGl2PkFjZWU8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBz
dHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9udC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVm
dDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDog
bWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGluOyBQQURE
SU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklH
SFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdl
aWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+S2VudCBXYXRzZW4gJmx0OzxhIGhyZWY9Im1haWx0bzpr
d2F0c2VuQGp1bmlwZXIubmV0Ij5rd2F0c2VuQGp1bmlwZXIubmV0PC9hPiZndDs8YnI+DQo8c3Bh
biBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RGF0ZTogPC9zcGFuPkZyaWRheSwgQXVndXN0IDI2
LCAyMDE2IGF0IDE6NTggUE08YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+VG86
IDwvc3Bhbj5MYWRpc2xhdiBMaG90a2EgJmx0OzxhIGhyZWY9Im1haWx0bzpsaG90a2FAbmljLmN6
Ij5saG90a2FAbmljLmN6PC9hPiZndDssIEFjZWUgTGluZGVtICZsdDs8YSBocmVmPSJtYWlsdG86
YWNlZUBjaXNjby5jb20iPmFjZWVAY2lzY28uY29tPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+Q2M6IDwvc3Bhbj4mcXVvdDs8YSBocmVmPSJtYWlsdG86bmV0bW9k
QGlldGYub3JnIj5uZXRtb2RAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86
bmV0bW9kQGlldGYub3JnIj5uZXRtb2RAaWV0Zi5vcmc8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0i
bWFpbHRvOm5ldG1vZC1jaGFpcnNAaWV0Zi5vcmciPm5ldG1vZC1jaGFpcnNAaWV0Zi5vcmc8L2E+
JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bmV0bW9kLWNoYWlyc0BpZXRmLm9yZyI+bmV0bW9k
LWNoYWlyc0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJv
bGQiPlN1YmplY3Q6IDwvc3Bhbj5SZWdhcmRpbmcgSVBSIG9uIGRyYWZ0LWlldGYtbmV0bW9kLXJv
dXRpbmctY2ZnLTIzPGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
aWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVG
VDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8
ZGl2IHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1s
bnM6dz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0
cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0
cDovL3d3dy53My5vcmcvVFIvUkVDLWh0bWw0MCI+DQo8bWV0YSBuYW1lPSJUaXRsZSIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IktleXdvcmRzIiBjb250ZW50PSIiPg0KPG1ldGEgbmFtZT0iR2Vu
ZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8
c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIg
NCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05v
cm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7fQ0KYTpsaW5rLCBz
cGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjND
MTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBl
cmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFp
blRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1z
dHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTt9DQpz
cGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWls
eTpDYWxpYnJpOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21z
by1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTt9DQpz
cGFuLm1zb0lucw0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUtbmFt
ZToiIjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6Q2Fs
aWJyaTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2lu
OjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjxkaXYgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVT
IiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlv
bjEiPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QXV0aG9ycywgQ29udHJpYnV0b3JzLCBXRyw8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QXMgcGFydCBvZiB0aGUgV0cgTGFzdCBDYWxs
LCBhcmUgeW91IGF3YXJlIG9mIGFueSBJUFIgdGhhdCBhcHBsaWVzIHRvIGRyYWZ0IGlkZW50aWZp
ZWQgYWJvdmU/Jm5ic3A7IFBsZWFzZSBzdGF0ZSBlaXRoZXI6PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jm5ic3A7ICogJnF1b3Q7Tm8sIEknbSBub3QgYXdhcmUgb2YgYW55IElQUiB0aGF0
IGFwcGxpZXMgdG8gdGhpcyBkcmFmdCZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7ICogJnF1b3Q7WWVzLCBJJ20gYXdhcmUgb2YgSVBSIHRoYXQgYXBw
bGllcyB0byB0aGlzIGRyYWZ0JnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPklm
IOKAnHllc+KAnSwgaGFzIHRoaXMgSVBSIGJlZW4gZGlzY2xvc2VkIGluIGNvbXBsaWFuY2Ugd2l0
aCBJRVRGIElQUiBydWxlcyAoc2VlIFJGQ3MgMzk3OSwgNDg3OSwgMzY2OSBhbmQgNTM3OCBmb3Ig
bW9yZSBkZXRhaWxzKT8gJm5ic3A7Jm5ic3A7UGxlYXNlIHN0YXRlIGVpdGhlcjo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyAqICZxdW90O1llcywgdGhlIElQ
UiBoYXMgYmVlbiBkaXNjbG9zZWQgaW4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzJnF1
b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsgKiAmcXVv
dDtObywgdGhlIElQUiBoYXMgbm90IGJlZW4gZGlzY2xvc2VkJnF1b3Q7PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPklmIHlvdSBhbnN3ZXIg4oCcbm/igJ0sIHBsZWFzZSBwcm92aWRlIGFu
eSBhZGRpdGlvbmFsIGRldGFpbHMgeW91IHRoaW5rIGFwcHJvcHJpYXRlLjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5JZiB5b3UgYXJlIGxpc3RlZCBhcyBhIGRvY3VtZW50IGF1dGhvciBv
ciBjb250cmlidXRvciwgcGxlYXNlIGFuc3dlciB0aGUgYWJvdmUgYnkgcmVzcG9uZGluZyB0byB0
aGlzIGVtYWlsIHJlZ2FyZGxlc3Mgb2Ygd2hldGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBh
bnkgcmVsZXZhbnQgSVBSLiBUaGlzIGRvY3VtZW50IHdpbGwgbm90IGFkdmFuY2UgdG8gdGhlIG5l
eHQgc3RhZ2UgdW50aWwgYSByZXNwb25zZQ0KIGhhcyBiZWVuIHJlY2VpdmVkIGZyb20gZWFjaCBh
dXRob3IgYW5kIGxpc3RlZCBjb250cmlidXRvci4gTk9URTogVEhJUyBBUFBMSUVTIFRPIEFMTCBP
RiBZT1UgTElTVEVEIElOIFRISVMgTUVTU0FHRSdTIFRPIExJTkVTLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij5JZiB5b3UgYXJlIG9uIHRoZSBXRyBlbWFpbCBsaXN0IG9yIGF0dGVuZCBX
RyBtZWV0aW5ncyBidXQgYXJlIG5vdCBsaXN0ZWQgYXMgYW4gYXV0aG9yIG9yIGNvbnRyaWJ1dG9y
LCB3ZSByZW1pbmQgeW91IG9mIHlvdXIgb2JsaWdhdGlvbnMgdW5kZXIgdGhlIElFVEYgSVBSIHJ1
bGVzIHdoaWNoIGVuY291cmFnZXMgeW91IHRvIG5vdGlmeSB0aGUgSUVURiBpZiB5b3UgYXJlIGF3
YXJlIG9mIElQUiBvZiBvdGhlcnMNCiBvbiBhbiBJRVRGIGNvbnRyaWJ1dGlvbiwgb3IgdG8gcmVm
cmFpbiBmcm9tIHBhcnRpY2lwYXRpbmcgaW4gYW55IGNvbnRyaWJ1dGlvbiBvciBkaXNjdXNzaW9u
IHJlbGF0ZWQgdG8geW91ciB1bmRpc2Nsb3NlZCBJUFIuIEZvciBtb3JlIGluZm9ybWF0aW9uLCBw
bGVhc2Ugc2VlIHRoZSBSRkNzIGxpc3RlZCBhYm92ZSBhbmQNCjxhIGhyZWY9Imh0dHA6Ly90cmFj
LnRvb2xzLmlldGYub3JnL2dyb3VwL2llc2cvdHJhYy93aWtpL0ludGVsbGVjdHVhbFByb3BlcnR5
Ij5odHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9ncm91cC9pZXNnL3RyYWMvd2lraS9JbnRlbGxl
Y3R1YWxQcm9wZXJ0eTwvYT4uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlBTOiBQbGVh
c2UgaW5jbHVkZSBhbGwgbGlzdGVkIGluIHRoZSBoZWFkZXJzIG9mIHRoaXMgbWVzc2FnZSBpbiB5
b3VyIHJlc3BvbnNlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5UaGFuayB5b3UsPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5ORVRNT0QgV0cgQ2hhaXJzPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_D3E612227B6E6aceeciscocom_--


From nobody Fri Aug 26 13:13:46 2016
Return-Path: <ivandean@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E99712D80A; Fri, 26 Aug 2016 13:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 vk1yw56y_Qdm; Fri, 26 Aug 2016 13:13:41 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 A72BE12D74F; Fri, 26 Aug 2016 13:13:40 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id q128so6315793wma.1; Fri, 26 Aug 2016 13:13:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=luU9JPb4n8QvhLdEIaV3UH/cHw3gw52VuKEgl+3DFOw=; b=qpHazMBJU38gLNPjMMonhu7IGViEmb7VGSI6bYgIKukrCwBrfdRe/szg071lOzmRls HnejEnquJf0w1PZ2r06oLKuOjhHcqRl+TQswWYqFZyd4eddgi3uqWFH/y91Jm3nZ5K1i t6Tye+oKksDsjKx8xpJSUwute81n4nabyL2grDVeoJceQvprWdHK9mgFbYtNauhgZXo9 ThetHvf7OX/ESiKO2TLHTCOco8fV0ti1BonujLQH+865wlh64KiYZF6VE2DKtdqJdt1d K7K9qWoyX2tQ/uI2knAdGdPr9IKT8n530hmRYfMxXTWEbfkICc9Es1MXRAhpnul5cDKp pgfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=luU9JPb4n8QvhLdEIaV3UH/cHw3gw52VuKEgl+3DFOw=; b=jMml/mNPpQZCTvn0P+cjerE0CT2MCvxUUznmoI9PGIu3WuKFhfeFhsO6soVKjtRkv0 zcdVdKQW4+M5H48w930N5l2/sVTFS7fuvsnpuakOyuZbPVG2pHgxyiR1aweYmRd90hJs HnWT26hpTB5jYoF037v+ncMa7uu0yBHOEWlAiRgh4s+PRxRf4Stesnh5JjyaqdfV/D4X eOg2eFv2dWjnbomSMiPP7i2B3RsdDZP8xu4CuxwonYVOm+iifpiOHGD4uMlFWfmzNnFl kq0eYXblQY0I1GBh98E9V5eXynfUuLr6JenBC20yNc1XeIggw9ws4SmNgmlvPsL1vFt/ Td+A==
X-Gm-Message-State: AE9vXwPgl8zUERHdy29d+/we99OSLWRSja1CqCFr63lMMhi4ON2Xwzt3JdqmRSL23Zh9uQ==
X-Received: by 10.28.208.140 with SMTP id h134mr503857wmg.101.1472242419037; Fri, 26 Aug 2016 13:13:39 -0700 (PDT)
Received: from [192.168.1.67] (82.red-83-53-209.dynamicip.rima-tde.net. [83.53.209.82]) by smtp.gmail.com with ESMTPSA id q65sm545473wmd.24.2016.08.26.13.13.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 26 Aug 2016 13:13:38 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9EA73B18-5C1C-4739-8770-F2D8F698BD25"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: [netmod] Regarding IPR on draft-ietf-netmod-routing-cfg-23
From: Dean Bogdanovic <ivandean@gmail.com>
In-Reply-To: <D3E61222.7B6E6%acee@cisco.com>
Date: Fri, 26 Aug 2016 22:13:38 +0200
Message-Id: <40874329-7ED8-41C0-A26C-90866BEC9EE1@gmail.com>
References: <5E95D548-556B-481F-BC97-4C7E2FB876CF@juniper.net> <D3E61222.7B6E6%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/ToLF6kQpRwTG9zx9SwOZpkxFFok>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 20:13:43 -0000

--Apple-Mail=_9EA73B18-5C1C-4739-8770-F2D8F698BD25
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Speaker as a contributor

No, I=E2=80=99m not aware of any IPR that applies to this draft

Dean
=20
> On Aug 26, 2016, at 9:35 PM, Acee Lindem (acee) <acee@cisco.com> =
wrote:
>=20
> Speaker as an author,
>=20
> No, I am not aware of an IPR that applies to this draft.=20
>=20
> Thanks,
> Acee
>=20
> From: Kent Watsen <kwatsen@juniper.net <mailto:kwatsen@juniper.net>>
> Date: Friday, August 26, 2016 at 1:58 PM
> To: Ladislav Lhotka <lhotka@nic.cz <mailto:lhotka@nic.cz>>, Acee =
Lindem <acee@cisco.com <mailto:acee@cisco.com>>
> Cc: "netmod@ietf.org <mailto:netmod@ietf.org>" <netmod@ietf.org =
<mailto:netmod@ietf.org>>, "netmod-chairs@ietf.org =
<mailto:netmod-chairs@ietf.org>" <netmod-chairs@ietf.org =
<mailto:netmod-chairs@ietf.org>>
> Subject: Regarding IPR on draft-ietf-netmod-routing-cfg-23
>=20
> Authors, Contributors, WG,
> =20
> As part of the WG Last Call, are you aware of any IPR that applies to =
draft identified above?  Please state either:
>   * "No, I'm not aware of any IPR that applies to this draft"
>   * "Yes, I'm aware of IPR that applies to this draft"
> =20
> If =E2=80=9Cyes=E2=80=9D, has this IPR been disclosed in compliance =
with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more =
details)?   Please state either:
>   * "Yes, the IPR has been disclosed in compliance with IETF IPR =
rules"
>   * "No, the IPR has not been disclosed"
> =20
> If you answer =E2=80=9Cno=E2=80=9D, please provide any additional =
details you think appropriate.
> =20
> If you are listed as a document author or contributor, please answer =
the above by responding to this email regardless of whether or not you =
are aware of any relevant IPR. This document will not advance to the =
next stage until a response has been received from each author and =
listed contributor. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS =
MESSAGE'S TO LINES.
> =20
> If you are on the WG email list or attend WG meetings but are not =
listed as an author or contributor, we remind you of your obligations =
under the IETF IPR rules which encourages you to notify the IETF if you =
are aware of IPR of others on an IETF contribution, or to refrain from =
participating in any contribution or discussion related to your =
undisclosed IPR. For more information, please see the RFCs listed above =
and http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty =
<http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty>.
> =20
> PS: Please include all listed in the headers of this message in your =
response.
> =20
> Thank you,
> NETMOD WG Chairs
> =20
> =20
> =20
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod


--Apple-Mail=_9EA73B18-5C1C-4739-8770-F2D8F698BD25
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Speaker as a contributor</div><div =
class=3D""><br class=3D""></div>No, I=E2=80=99m not aware of any IPR =
that applies to this draft<div class=3D""><br class=3D""></div><div =
class=3D"">Dean</div><div class=3D"">&nbsp;<br class=3D""><div><blockquote=
 type=3D"cite" class=3D""><div class=3D"">On Aug 26, 2016, at 9:35 PM, =
Acee Lindem (acee) &lt;<a href=3D"mailto:acee@cisco.com" =
class=3D"">acee@cisco.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">Speaker as an =
author,</div><div style=3D"font-family: Calibri, sans-serif; font-size: =
14px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><div style=3D"font-family: Calibri, sans-serif; =
font-size: 14px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">No, =
I am not aware of an IPR that applies to this draft.&nbsp;</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><br class=3D""></div><div=
 style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">Thanks,</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">Acee</div><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: =
Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><div style=3D"font-family: Calibri; font-size: 11pt; =
text-align: left; border-width: 1pt medium medium; border-style: solid =
none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" =
class=3D""><span style=3D"font-weight: bold;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Kent Watsen &lt;<a =
href=3D"mailto:kwatsen@juniper.net" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">kwatsen@juniper.net</a>&gt;<br =
class=3D""><span style=3D"font-weight: bold;" class=3D"">Date:<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Friday, August 26, =
2016 at 1:58 PM<br class=3D""><span style=3D"font-weight: bold;" =
class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Ladislav Lhotka =
&lt;<a href=3D"mailto:lhotka@nic.cz" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">lhotka@nic.cz</a>&gt;, Acee =
Lindem &lt;<a href=3D"mailto:acee@cisco.com" style=3D"color: rgb(149, =
79, 114); text-decoration: underline;" =
class=3D"">acee@cisco.com</a>&gt;<br class=3D""><span =
style=3D"font-weight: bold;" class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></span>"<a =
href=3D"mailto:netmod@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">netmod@ietf.org</a>" &lt;<a =
href=3D"mailto:netmod@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">netmod@ietf.org</a>&gt;, "<a =
href=3D"mailto:netmod-chairs@ietf.org" style=3D"color: rgb(149, 79, =
114); text-decoration: underline;" class=3D"">netmod-chairs@ietf.org</a>" =
&lt;<a href=3D"mailto:netmod-chairs@ietf.org" style=3D"color: rgb(149, =
79, 114); text-decoration: underline;" =
class=3D"">netmod-chairs@ietf.org</a>&gt;<br class=3D""><span =
style=3D"font-weight: bold;" class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Regarding IPR on =
draft-ietf-netmod-routing-cfg-23<br class=3D""></div><div class=3D""><br =
class=3D""></div><blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"border-left-color: rgb(181, 196, 223); border-left-width: 5px; =
border-left-style: solid; padding: 0px 0px 0px 5px; margin: 0px 0px 0px =
5px;" class=3D""><div xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40" class=3D""><div =
bgcolor=3D"white" lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" =
class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1;"><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri;" class=3D"">Authors, Contributors, WG,<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">As part of the WG =
Last Call, are you aware of any IPR that applies to draft identified =
above?&nbsp; Please state either:</div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri;" class=3D"">&nbsp; * =
"No, I'm not aware of any IPR that applies to this draft"<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">&nbsp; * "Yes, I'm =
aware of IPR that applies to this draft"<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri;" class=3D"">If =E2=80=9Cyes=E2=80=9D, has this IPR been =
disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 =
and 5378 for more details)? &nbsp;&nbsp;Please state either:<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">&nbsp; * "Yes, the =
IPR has been disclosed in compliance with IETF IPR rules"<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">&nbsp; * "No, the IPR =
has not been disclosed"<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">If you answer =
=E2=80=9Cno=E2=80=9D, please provide any additional details you think =
appropriate.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">If you are listed as =
a document author or contributor, please answer the above by responding =
to this email regardless of whether or not you are aware of any relevant =
IPR. This document will not advance to the next stage until a response =
has been received from each author and listed contributor. NOTE: THIS =
APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">If you are on the WG =
email list or attend WG meetings but are not listed as an author or =
contributor, we remind you of your obligations under the IETF IPR rules =
which encourages you to notify the IETF if you are aware of IPR of =
others on an IETF contribution, or to refrain from participating in any =
contribution or discussion related to your undisclosed IPR. For more =
information, please see the RFCs listed above and<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProper=
ty" style=3D"color: rgb(149, 79, 114); text-decoration: underline;" =
class=3D"">http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualPro=
perty</a>.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">PS: Please include =
all listed in the headers of this message in your response.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">Thank you,<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D"">NETMOD WG Chairs<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div></div></blockquote></span><span =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D""></span><span style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: =
none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">netmod mailing list</span><br =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D""><a href=3D"mailto:netmod@ietf.org" =
class=3D"">netmod@ietf.org</a></span><br style=3D"font-family: Calibri, =
sans-serif; font-size: 14px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Calibri, sans-serif; font-size: =
14px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/netmod" =
class=3D"">https://www.ietf.org/mailman/listinfo/netmod</a></span></div></=
blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_9EA73B18-5C1C-4739-8770-F2D8F698BD25--


From nobody Mon Aug 29 16:29:02 2016
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49FBC12D8B2 for <rtgwg@ietfa.amsl.com>; Mon, 29 Aug 2016 16:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 15gxQf3RWDfw for <rtgwg@ietfa.amsl.com>; Mon, 29 Aug 2016 16:28:58 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (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 88D6912D871 for <rtgwg@ietf.org>; Mon, 29 Aug 2016 16:28:58 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id x72so951499pfd.2 for <rtgwg@ietf.org>; Mon, 29 Aug 2016 16:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=nwp/f3ooi/d9zGwovsJxNwZiY6Pj7swHIdwaJ/Ks+50=; b=wxEmTKgftGfxNh0SQn82IRvWi3lVOJoEvB2HZn7tE5ppehbi1otf8xO7zwZmzH9YX7 KglzBNG4OMT0H1GX7v9VniEK2KpCIJDw6Cq7j0W1J1ZWVTcGTFd/ZcX8BW8guCxPYCOT dA9YjJgDljFWoj0PuNDVPcvjs1TMRI8zqcx38Okpe0PGwMB3/9fSvD4PtTpPLh2vloKu vydx0XS4nr3ZhBooYvnGWWhHfRrbL4/2xDom6WlHzZEUHuHChM4S3NO+dX+wwiRrhUiv MbIEN3PiUk5VcsyMiS391HGxqMlKZFWYjb9Z4N0PEmXcR1ds/rTxCeOxKH92XndAoKfI LhWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=nwp/f3ooi/d9zGwovsJxNwZiY6Pj7swHIdwaJ/Ks+50=; b=AZ14hqc2UyESSRCXp3FiOfPZsSin3BfNbH6pMkYrwvXb1ZGND3uLYBb2eSH/EBxa2C SSOFpsSIBLkncDGFYdXaKRSyR9q5Gn/fYjTLexuuXDh0ezoYNPJgCcfBZHPSQ2lPFWgB ZHJeSVxUdam0Vg9DOZffxVGbQtDBv9OVu09Une4Gi0/Pb4U10do7ZeJKq1o8OZ815ywL 1lXsyWV7Rs+8y8nhoKiWx2VMGQm5s3nDDeaLuS6h59/uU+GGHp1E0SPxYNi818s7N3IW hFaICRSonGOfnxvQqFrWm5QkPGukOQsGuWtrKrD3kYOG3CVC5aTKcmolclDuuWvYXRHO 8fOg==
X-Gm-Message-State: AE9vXwNK/VBfLe50V9pgxxhhZQ+CO+COyoZ8G+qVdKZP6i4AZGo7QbYUPsnhXcYVduhIfQ==
X-Received: by 10.98.152.129 with SMTP id d1mr994513pfk.126.1472513337814; Mon, 29 Aug 2016 16:28:57 -0700 (PDT)
Received: from [192.168.254.3] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id yj6sm449702pab.8.2016.08.29.16.28.56 for <rtgwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Aug 2016 16:28:57 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.17.0.160611
Date: Mon, 29 Aug 2016 16:29:25 -0700
Subject: NomCom 2016-2017: Call for Nominations
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>
Message-ID: <9112228E-4643-4716-B3FD-17E23B588F67@gmail.com>
Thread-Topic: NomCom 2016-2017: Call for Nominations
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3555332966_282942162"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/RyXYQtd8opqrmtrsRWZoJEhNHL0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 23:29:01 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3555332966_282942162
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Dear RTGWG

=20

The 2016-17 Nominating Committee (Nomcom) is seeking nominations from

now until October 8, 2016. The open positions being considered by this

year's Nomcom can be found at the end of this email and also on this

year's Nomcom website:

=20

https://datatracker.ietf.org/nomcom/2016/

=20

Nominations may be made by selecting the Nominate link at the top of

the Nomcom 2016 home page, or by visiting the following URL:

=20

https://datatracker.ietf.org/nomcom/2016/nominate/

=20

=C2=A0=C2=A0 {Note that nominations made using the web tool require an ietf.org

=C2=A0=C2=A0=C2=A0 datatracker account. You can create a datatracker ietf.org account

=C2=A0=C2=A0=C2=A0 if you don't have one already by visiting the following URL:

=C2=A0=C2=A0=C2=A0 https://datatracker.ietf.org/accounts/create/ }

=20

If you are unable to use the web form, nominations may instead be made

by email to nomcom-16@ietf.org. If using email, please include the word

"Nominate" in the Subject and indicate in the email who is being

nominated, their email address (to confirm acceptance of the

nomination), and the position for which you are making the nomination.

If you are nominating someone other than yourself, please tell us if

we may tell the nominee that you were the one who made the nomination.

If you wish to nominate someone via email for more than one position,

please use separate emails to do so.

=20

Self-nomination is welcome!

=20

Willing nominees will be asked to fill out a questionnaire

specific to the position for which they are nominated.=C2=A0 The questionnaires

will be available on September 2, 2016 and have a submission deadline of

October 13, 2016.

=20

NomCom 2016-17 will follow the policy for "Open Disclosure of Willing

Nominees" described in BCP 10/RFC 7437.=C2=A0 As stated in RFC 7437: "The

list of nominees willing to be considered for positions under review

in the current Nomcom cycle is not confidential". Willing nominees for

each position will be listed in a publicly accessible way - anyone

with a datatracker account may access the lists.=C2=A0 Additionally, the

nomination form asks if we may share your own name with the

nominee. In all other ways, the confidentiality requirements of BCP10

remain in effect.=C2=A0 All feedback and all Nomcom deliberations will

remain confidential and will not be disclosed.

=20

There is a field on the form you can mark in order to allow the Nomcom

to tell the nominee that you were the one who made the

nomination. This defaults to =E2=80=9Cno=E2=80=9D - so if you don't mark the field

we won=E2=80=99t tell.

=20

In order to ensure time to collect sufficient community feedback about

each of the willing nominees, nominations must be received by the

NomCom on or before October 8, 2016.

=20

Please submit your nominations as early as possible for the sake of

your nominees. Note that nominations should not wait for management

permission, as it is easier to decline the nomination than put one in

late.

=20

The Nomcom appoints individuals to fill the open slots on the IAOC,

the IAB, and the IESG. The list of people and posts whose terms end

with the March 2017 IETF meeting, and thus the positions for which

this Nomcom is responsible, follows:

=20

IAOC

=20

=C2=A0=C2=A0=C2=A0=C2=A0 Lou Berger

=20

IAB

=20

=C2=A0=C2=A0=C2=A0=C2=A0 Ralph Droms*

=C2=A0=C2=A0=C2=A0=C2=A0 Russ Housley*

=C2=A0=C2=A0=C2=A0=C2=A0 Robert Sparks

=C2=A0=C2=A0=C2=A0=C2=A0 Andrew Sullivan

=C2=A0=C2=A0=C2=A0=C2=A0 Dave Thaler*

=C2=A0=C2=A0=C2=A0=C2=A0 Suzanne Woolf

=20

IESG

=20

=C2=A0=C2=A0=C2=A0=C2=A0 Jari Arkko (GEN)*

=C2=A0=C2=A0=C2=A0=C2=A0 Deborah Brungard (RTG)

=C2=A0=C2=A0=C2=A0=C2=A0 Ben Campbell (ART)

=C2=A0=C2=A0=C2=A0=C2=A0 Spencer Dawkins (TSV)

=C2=A0=C2=A0=C2=A0=C2=A0 Stephen Farrell (SEC)*

=C2=A0=C2=A0=C2=A0=C2=A0 Joel Jaeggli (OPS)*

=C2=A0=C2=A0=C2=A0=C2=A0 Terry Manderson (INT)

=C2=A0=C2=A0=C2=A0=C2=A0 Alvaro Retana (RTG)

=20

*- have indicated that they do not intend to accept a

renomination. This information is always up to date on

https://datatracker.ietf.org/nomcom/2016/

=20

Please be resourceful in identifying possible candidates for these

positions, as developing our talent is a very crucial requirement for

the IETF, and also, please consider accepting a nomination.=C2=A0 You'll

find extensive information about specific positions, developed by the

IAB, IESG, and IAOC, under individual tabs at:

=20

=C2=A0=C2=A0 https://datatracker.ietf.org/nomcom/2016/requirements/

=20

In addition to nominations, the Nomcom seeks community input on the

positions themselves.=C2=A0 We need and welcome the community's views and

input on the jobs within each organization. If you have ideas on the

positions' responsibilities (more, less, different), please let us

know.

=20

Please send suggestions and feedback about this to nomcom-16@ietf.org.

=20

Thank you for your help in identifying qualified nominees!

=20

Lucy Lynch

Nomcom Chair 2016-17

nomcom-chair-2016@ietf.org

llynch@civil-tongue.net

=20

=20

Cheers,

Jeff

=20


--B_3555332966_282942162
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Calibri;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:Calibri;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>Dear RTGWG<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt'>The 2016-17 Nominating Committee (Nomcom) is seeking nominations =
from<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=
now until October 8, 2016. The open positions being considered by this<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>year's Nom=
com can be found at the end of this email and also on this<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>year's Nomcom website:=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>ht=
tps://datatracker.ietf.org/nomcom/2016/<o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt'>Nominations may be made by selecting th=
e Nominate link at the top of<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>the Nomcom 2016 home page, or by visiting the follo=
wing URL:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt'>https://datatracker.ietf.org/nomcom/2016/nominate/<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0 {Note that nomin=
ations made using the web tool require an ietf.org<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0 datatracker account. Yo=
u can create a datatracker ietf.org account<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0 if you don't have one already =
by visiting the following URL:<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0 https://datatracker.ietf.org/accounts/creat=
e/ }<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
'>If you are unable to use the web form, nominations may instead be made<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>by email=
 to nomcom-16@ietf.org. If using email, please include the word<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&quot;Nominate&qu=
ot; in the Subject and indicate in the email who is being<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>nominated, their email =
address (to confirm acceptance of the<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt'>nomination), and the position for which you=
 are making the nomination.<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>If you are nominating someone other than yourself, pl=
ease tell us if<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt'>we may tell the nominee that you were the one who made the nomina=
tion.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'=
>If you wish to nominate someone via email for more than one position,<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>please use=
 separate emails to do so.<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt'>Self-nomination is welcome!<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Willing nominees will be as=
ked to fill out a questionnaire<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt'>specific to the position for which they are nomin=
ated.=C2=A0 The questionnaires<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'>will be available on September 2, 2016 and have a subm=
ission deadline of<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt'>October 13, 2016.<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt'>NomCom 2016-17 will follow the policy for &quot=
;Open Disclosure of Willing<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>Nominees&quot; described in BCP 10/RFC 7437.=C2=A0 As sta=
ted in RFC 7437: &quot;The<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'>list of nominees willing to be considered for position=
s under review<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:11.0pt'>in the current Nomcom cycle is not confidential&quot;. Willing nom=
inees for<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt'>each position will be listed in a publicly accessible way - anyone<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>with a da=
tatracker account may access the lists.=C2=A0 Additionally, the<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>nomination form asks =
if we may share your own name with the<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:11.0pt'>nominee. In all other ways, the confidenti=
ality requirements of BCP10<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>remain in effect.=C2=A0 All feedback and all Nomcom delib=
erations will<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt'>remain confidential and will not be disclosed.<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>There is a field on the=
 form you can mark in order to allow the Nomcom<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt'>to tell the nominee that you were=
 the one who made the<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'>nomination. This defaults to &#8220;no&#8221; - so if you d=
on't mark the field<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt'>we won&#8217;t tell.<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt'>In order to ensure time to collect sufficie=
nt community feedback about<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>each of the willing nominees, nominations must be rec=
eived by the<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt'>NomCom on or before October 8, 2016.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt'>Please submit your nominations as =
early as possible for the sake of<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt'>your nominees. Note that nominations should not=
 wait for management<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt'>permission, as it is easier to decline the nomination than p=
ut one in<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt'>late.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt'>The Nomcom appoints individuals to fill the open slots on the IAOC,<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>the I=
AB, and the IESG. The list of people and posts whose terms end<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>with the March 201=
7 IETF meeting, and thus the positions for which<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt'>this Nomcom is responsible, foll=
ows:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
'>IAOC<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Lou Berger<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt'>IAB<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Ralph Droms*<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Russ Housley*<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Robert Spa=
rks<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=
=A0=C2=A0=C2=A0=C2=A0 Andrew Sullivan<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Dave Thaler*<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Suzanne Woolf<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>IESG<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Jari Arkk=
o (GEN)*<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Deborah Brungard (RTG)<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Ben Campbell (ART)<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Spencer Dawki=
ns (TSV)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Stephen Farrell (SEC)*<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Joel Jaeggli (OPS)*<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Terry Mander=
son (INT)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt'>=C2=A0=C2=A0=C2=A0=C2=A0 Alvaro Retana (RTG)<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'>*- have indicated that they do not intend to =
accept a<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt'>renomination. This information is always up to date on<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>https://datatracker.ie=
tf.org/nomcom/2016/<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'>Please be resourceful in identifying possible candidates fo=
r these<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>positions, as developing our talent is a very crucial requirement for<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>the IETF=
, and also, please consider accepting a nomination.=C2=A0 You'll<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>find extensive infor=
mation about specific positions, developed by the<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt'>IAB, IESG, and IAOC, under indi=
vidual tabs at:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt'>=C2=A0=C2=A0 https://datatracker.ietf.org/nomcom/2016/requirements/<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>In add=
ition to nominations, the Nomcom seeks community input on the<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>positions themselve=
s.=C2=A0 We need and welcome the community's views and<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt'>input on the jobs within each =
organization. If you have ideas on the<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:11.0pt'>positions' responsibilities (more, less, d=
ifferent), please let us<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'>know.<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>Please send suggestions and feedback about this to no=
mcom-16@ietf.org.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt'>Thank you for your help in identifying qualified nominees!<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Lucy =
Lynch<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'=
>Nomcom Chair 2016-17<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'>nomcom-chair-2016@ietf.org<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt'>llynch@civil-tongue.net<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;col=
or:black'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:10.5pt;color:black'>Jeff<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div></body></html>

--B_3555332966_282942162--



From nobody Tue Aug 30 04:19:09 2016
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9EA12D176; Tue, 30 Aug 2016 04:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
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 2XwEUQIWP8V5; Tue, 30 Aug 2016 04:19:01 -0700 (PDT)
Received: from mail-ua0-x242.google.com (mail-ua0-x242.google.com [IPv6:2607:f8b0:400c:c08::242]) (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 A947D12D0BB; Tue, 30 Aug 2016 04:19:01 -0700 (PDT)
Received: by mail-ua0-x242.google.com with SMTP id 35so1138256uaj.3; Tue, 30 Aug 2016 04:19:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=FW3ufvYxGlALYGdAB2PJYfoAJurWr91VcDtJTn62New=; b=b7ARFOJ7CncOrXEJ2/2AdTQTZue9lPMeNSApgH7PBkubbmXKrE+JL1eIqCOcu7binI e19+ZsypkOAKpWjDo4M4OAu5CNcgDJnr11I6RxxOwcWRqIQMYo0qx0SuPg6RLvVti7Al 4t3Sdpxkl1xwttDBaVzdt9ZjMmDzjC5CwwMuQfpKqpIic7HkkDXVVcTOb+iqDWWznneS aOx8ZUX/PtyqzTgKX+Y7zlD2awsoU9IXdGd90/OE7rqtrsPFenMFFVVbRdIK5FmkuGWI pdsROgLpHZNO8P4XWbwbQFxywwOLdxey9zixajK/X2/XbE9fcmbRyJjj9f9NfTH6yis6 o5tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=FW3ufvYxGlALYGdAB2PJYfoAJurWr91VcDtJTn62New=; b=AEOemGy+OOITOogI0cpxa6iLmrNeEHDOmt9FGnWXXifvGjFsjKU7P0wXtROF0v7Gut 2sQM9iIl/G5Z7wheKAOsVm6gXGNGmmAV1Sfi4z4VnJ3+A09zaf39mZXBp7CNGc+ZBK6n 7CsJse29FaiF38IS+FnGLLo9/3syWqzv9ZX2GV9eapfNA770aUTPpf6IyJGZcdiw6qGF Eb/4TidHTpI4NPEt2/ucS0ceirPq0gc/+CtqJpF0KcBiXe+XkMifPxdiR5dPiIY+cQe+ JW/SwB0mdt3+2zj1vaVYLYq96U6hIY0ameYR2608JlSQ2ZHA4b5517bUC0mzuhLt8zDe AIBg==
X-Gm-Message-State: AE9vXwMXWnxMY+77loHQr4QMXxlifUakrBF8OKzH3LuFNRrSNnVt1vAYqeK0WkBwQiRl4i8ccJTYFU/hVmZrrw==
X-Received: by 10.31.164.73 with SMTP id n70mr1737793vke.15.1472555940747; Tue, 30 Aug 2016 04:19:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.36.172 with HTTP; Tue, 30 Aug 2016 04:19:00 -0700 (PDT)
From: Ines  Robles <mariainesrobles@googlemail.com>
Date: Tue, 30 Aug 2016 14:19:00 +0300
Message-ID: <CAP+sJUfn6n0xR-AugT5=O2kXHj2K0WsPBeXqnP3GQJoD8Md=Xg@mail.gmail.com>
Subject: Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
To: jefftant.ietf@gmail.com, cbowers@juniper.net,  draft-ietf-rtgwg-yang-key-chain@ietf.org
Content-Type: multipart/alternative; boundary=001a1142701ec29f50053b4825b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/pHsCy3Pph3IyJ6m07soCOewcNbU>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 11:19:03 -0000

--001a1142701ec29f50053b4825b1
Content-Type: text/plain; charset=UTF-8

Hi,

Thank you for this work. I find the document readable and understandable.

Some comments:

Abstract:

- In this sentence "A key chain is... algorithm", I would add "A key chain
is... algorithm (authentication or encryption)".

Section 1. Introduction:

I would like to have an example on this statement:

" In some applications, the protocols do not use the key chain element key
  directly, but rather a key derivation function is used to derive a
  short-lived key from the key chain element key. e.g...." --> maybe
draft-bhatia-karp-short-lived-keys-00?


Section 1.1-

-I would add here the reference to RFC 6020, something like:

"The terminology for describing YANG data models is found in [RFC6020].

...

1.1.1.  Tree Diagrams

  A simplified graphical representation of the data model is used in
  the YANG modules specified in this document.  The meaning of the
  symbols in these diagrams is as follows:

     Brackets "[" and "]" enclose list keys.

     Abbreviations before data node names: "rw" means configuration
     data (read-write) and "ro" state data (read-only).

     Symbols after data node names: "?" means an optional node, "!"
     means a presence container, and "*" denotes a list and leaf-list.

     Parentheses enclose choice and case nodes, and case nodes are also
     marked with a colon (":").

     Ellipsis ("...") stands for contents of subtrees that are not
     shown." source of the text:
https://tools.ietf.org/html/draft-vanderstok-roll-mpl-yang-01

- even when it is pretty obvious, I would add a reference to the key
definition [RFC4949 - page 171]


Section 5:

     It is empty, you mention some related work in section 2, but maybe you
could add in here a tree diagram such as the one showed in
https://tools.ietf.org/html/draft-ietf-netconf-server-model-09#section-3

Section 7

-For the XML-REGISTRY I would add a table with suggested values for the
respective columns of ns registry: ID, URI, Filename, Reference [
http://www.iana.org/assignments/xml-registry/xml-registry.xhtml#ns]
-For YANG Module Names registry, you have name, namespace, prefix and
reference, only there is a column missing which is module,  [
http://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml#yang-parameters-1
]
- I would add an informative reference to RFC5226. "Guidelines for Writing
an IANA Considerations Section in RFCs"


Additional questions:

- Should RFC 6518 be mentioned in this document? like the Cryptographic
Keys Life Cycle?

- What about ECC? Should it be included or it is not-related/out-of-scope?



Thank you,

Ines.

--001a1142701ec29f50053b4825b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>Thank you for this work.=
 I find the document readable and understandable.</div><div><br></div><div>=
Some comments:</div><div><br></div><div>Abstract:</div><div><br></div><div>=
<span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	</span>- In=
 this sentence &quot;A key chain is... algorithm&quot;, I would add &quot;A=
 key chain is... algorithm (authentication or encryption)&quot;.=C2=A0</div=
><div><br></div><div>Section 1. Introduction:</div><div><br></div><div><spa=
n class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	</span>I would =
like to have an example on this statement:</div><div><br></div><div><span c=
lass=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	</span>&quot; In s=
ome applications, the protocols do not use the key chain element key</div><=
div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	</span>=
 =C2=A0 directly, but rather a key derivation function is used to derive a<=
/div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	<=
/span> =C2=A0 short-lived key from the key chain element key. e.g....&quot;=
 --&gt; maybe draft-bhatia-karp-short-lived-keys-00?</div><div><br></div><d=
iv><br></div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space=
:pre">	</span>Section 1.1-</div><div><br></div><div><span class=3D"gmail-Ap=
ple-tab-span" style=3D"white-space:pre">		</span>-I would add here the refe=
rence to RFC 6020, something like:</div><div><br></div><div><span class=3D"=
gmail-Apple-tab-span" style=3D"white-space:pre">		</span> &quot;The termino=
logy for describing YANG data models is found in [RFC6020].</div><div><br><=
/div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		=
</span>...</div><div><br></div><div><span class=3D"gmail-Apple-tab-span" st=
yle=3D"white-space:pre">		</span>1.1.1.=C2=A0 Tree Diagrams</div><div><br><=
/div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		=
</span> =C2=A0 A simplified graphical representation of the data model is u=
sed in</div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:=
pre">		</span> =C2=A0 the YANG modules specified in this document.=C2=A0 Th=
e meaning of the</div><div><span class=3D"gmail-Apple-tab-span" style=3D"wh=
ite-space:pre">		</span> =C2=A0 symbols in these diagrams is as follows:</d=
iv><div><br></div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-=
space:pre">		</span> =C2=A0 =C2=A0 =C2=A0Brackets &quot;[&quot; and &quot;]=
&quot; enclose list keys.</div><div><br></div><div><span class=3D"gmail-App=
le-tab-span" style=3D"white-space:pre">		</span> =C2=A0 =C2=A0 =C2=A0Abbrev=
iations before data node names: &quot;rw&quot; means configuration</div><di=
v><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		</span> =
=C2=A0 =C2=A0 =C2=A0data (read-write) and &quot;ro&quot; state data (read-o=
nly).</div><div><br></div><div><span class=3D"gmail-Apple-tab-span" style=
=3D"white-space:pre">		</span> =C2=A0 =C2=A0 =C2=A0Symbols after data node =
names: &quot;?&quot; means an optional node, &quot;!&quot;</div><div><span =
class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		</span> =C2=A0 =
=C2=A0 =C2=A0means a presence container, and &quot;*&quot; denotes a list a=
nd leaf-list.</div><div><br></div><div><span class=3D"gmail-Apple-tab-span"=
 style=3D"white-space:pre">		</span> =C2=A0 =C2=A0 =C2=A0Parentheses enclos=
e choice and case nodes, and case nodes are also</div><div><span class=3D"g=
mail-Apple-tab-span" style=3D"white-space:pre">		</span> =C2=A0 =C2=A0 =C2=
=A0marked with a colon (&quot;:&quot;).</div><div><br></div><div><span clas=
s=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		</span> =C2=A0 =C2=
=A0 =C2=A0Ellipsis (&quot;...&quot;) stands for contents of subtrees that a=
re not</div><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:=
pre">		</span> =C2=A0 =C2=A0 =C2=A0shown.&quot; source of the text: <a href=
=3D"https://tools.ietf.org/html/draft-vanderstok-roll-mpl-yang-01">https://=
tools.ietf.org/html/draft-vanderstok-roll-mpl-yang-01</a></div><div><br></d=
iv><div><span class=3D"gmail-Apple-tab-span" style=3D"white-space:pre">		</=
span>- even when it is pretty obvious, I would add a reference to the key d=
efinition [RFC4949 - page 171]</div><div><br></div><div><br></div><div>Sect=
ion 5:</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0It is empty, you mentio=
n some related work in section 2, but maybe you could add in here a tree di=
agram such as the one showed in <a href=3D"https://tools.ietf.org/html/draf=
t-ietf-netconf-server-model-09#section-3">https://tools.ietf.org/html/draft=
-ietf-netconf-server-model-09#section-3</a>=C2=A0</div><div><br></div><div>=
Section 7</div><div><br></div><div><span class=3D"gmail-Apple-tab-span" sty=
le=3D"white-space:pre">	</span>-For the XML-REGISTRY I would add a table wi=
th suggested values for the respective columns of ns registry: ID, URI, Fil=
ename, Reference [<a href=3D"http://www.iana.org/assignments/xml-registry/x=
ml-registry.xhtml#ns">http://www.iana.org/assignments/xml-registry/xml-regi=
stry.xhtml#ns</a>]</div><div><span class=3D"gmail-Apple-tab-span" style=3D"=
white-space:pre">	</span>-For YANG Module Names registry, you have name, na=
mespace, prefix and reference, only there is a column missing which is modu=
le, =C2=A0[<a href=3D"http://www.iana.org/assignments/yang-parameters/yang-=
parameters.xhtml#yang-parameters-1">http://www.iana.org/assignments/yang-pa=
rameters/yang-parameters.xhtml#yang-parameters-1</a>]</div><div><span class=
=3D"gmail-Apple-tab-span" style=3D"white-space:pre">	</span>- I would add a=
n informative reference to RFC5226. &quot;Guidelines for Writing an IANA Co=
nsiderations Section in RFCs&quot;</div><div><br></div><div><br></div><div>=
Additional questions:</div><div><br></div><div>- Should RFC 6518 be mention=
ed in this document? like the Cryptographic Keys Life Cycle?<br></div><div>=
<br></div><div>- What about ECC? Should it be included or it is not-related=
/out-of-scope?</div><div><br></div><div><br></div><div><br></div><div>Thank=
 you,</div><div><br></div><div>Ines.</div><div><br></div></div>

--001a1142701ec29f50053b4825b1--


From nobody Tue Aug 30 09:24:20 2016
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2537412D66A; Tue, 30 Aug 2016 09:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.068
X-Spam-Level: 
X-Spam-Status: No, score=-15.068 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 oNwDMbFcvzzi; Tue, 30 Aug 2016 09:24:16 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E49812D6AD; Tue, 30 Aug 2016 09:10:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24549; q=dns/txt; s=iport; t=1472573455; x=1473783055; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=o5+9+Osg6JXbcK/iorg8EwPp95csh0Xj3QSzc5sY9YY=; b=h4geIuz2GJeXZJsa5v6/30Ukf644nz+eYOZELu0G6MpUMiNP9hR1g605 8Evbuvk4kpVKdY7/Elpj9gq/y6hl5+nmEYaAUGCDvFtKlZGR3dxPtZHHX QYlYH9DZVxhOgo3y0irDQoyfl+g4hJhgj/W8fEEpwWDQRCYSG0xJAcxBw M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DIAQAvr8VX/5FdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBgnYzAQEBAQEeV3wHjSeeUocnhQqCASaFdwIcgUI4FAECAQEBAQEBAV4nhGE?= =?us-ascii?q?BAQEEIwRSEAIBCA4DAwECGQ8DAgICHxEUCQgCBAENBQkQiBEDFw6ueItdDYM9A?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBHIp7gkOBZzYugjSCWgWOJIVlhRM0AYYfhj6?= =?us-ascii?q?CUIFtiBGFWYg/hAmDeAEeNoQwcAGFbH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,257,1470700800";  d="scan'208,217";a="141573934"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2016 16:10:54 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u7UGArg0002646 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 30 Aug 2016 16:10:54 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 30 Aug 2016 12:10:53 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 30 Aug 2016 12:10:52 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ines Robles <mariainesrobles@googlemail.com>, "jefftant.ietf@gmail.com" <jefftant.ietf@gmail.com>, "cbowers@juniper.net" <cbowers@juniper.net>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>
Subject: Re: Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
Thread-Topic: Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
Thread-Index: AQHSArBSv7GKJC8QREGcD0NB0+Cw6aBhrMUA
Date: Tue, 30 Aug 2016 16:10:52 +0000
Message-ID: <D3EB11E9.7C410%acee@cisco.com>
References: <CAP+sJUfn6n0xR-AugT5=O2kXHj2K0WsPBeXqnP3GQJoD8Md=Xg@mail.gmail.com>
In-Reply-To: <CAP+sJUfn6n0xR-AugT5=O2kXHj2K0WsPBeXqnP3GQJoD8Md=Xg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D3EB11E97C410aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/mde33EcIWiTmUrff7dQYRB1fOoA>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 16:24:19 -0000

--_000_D3EB11E97C410aceeciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSW5lcywNCg0KVGhhbmtzIGZvciB0aGUgcm91dGluZyBkaXJlY3RvcmF0ZSByZXZpZXcuIFNl
ZSBpbmxpbmUuDQoNCkZyb206IEluZXMgUm9ibGVzIDxtYXJpYWluZXNyb2JsZXNAZ29vZ2xlbWFp
bC5jb208bWFpbHRvOm1hcmlhaW5lc3JvYmxlc0Bnb29nbGVtYWlsLmNvbT4+DQpEYXRlOiBUdWVz
ZGF5LCBBdWd1c3QgMzAsIDIwMTYgYXQgNzoxOSBBTQ0KVG86IEplZmYgVGFudHN1cmEgPGplZmZ0
YW50LmlldGZAZ21haWwuY29tPG1haWx0bzpqZWZmdGFudC5pZXRmQGdtYWlsLmNvbT4+LCBDaHJp
cyBCb3dlcnMgPGNib3dlcnNAanVuaXBlci5uZXQ8bWFpbHRvOmNib3dlcnNAanVuaXBlci5uZXQ+
PiwgImRyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0
LWlldGYtcnRnd2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmc+IiA8ZHJhZnQtaWV0Zi1ydGd3Zy15
YW5nLWtleS1jaGFpbkBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1j
aGFpbkBpZXRmLm9yZz4+DQpDYzogSm9uYXRoYW4gSGFyZHdpY2sgPEpvbmF0aGFuLkhhcmR3aWNr
QG1ldGFzd2l0Y2guY29tPG1haWx0bzpKb25hdGhhbi5IYXJkd2lja0BtZXRhc3dpdGNoLmNvbT4+
LCBSb3V0aW5nIERpcmVjdG9yYXRlIDxydGctZGlyQGlldGYub3JnPG1haWx0bzpydGctZGlyQGll
dGYub3JnPj4sIFJvdXRpbmcgV0cgPHJ0Z3dnQGlldGYub3JnPG1haWx0bzpydGd3Z0BpZXRmLm9y
Zz4+DQpTdWJqZWN0OiBSb3V0aW5nIERpcmVjdG9yYXRlIFFBIHJldmlldyBvZiBkcmFmdC1pZXRm
LXJ0Z3dnLXlhbmcta2V5LWNoYWluDQpSZXNlbnQtRnJvbTogPGFsaWFzLWJvdW5jZXNAaWV0Zi5v
cmc8bWFpbHRvOmFsaWFzLWJvdW5jZXNAaWV0Zi5vcmc+Pg0KUmVzZW50LVRvOiBBY2VlIExpbmRl
bSA8YWNlZUBjaXNjby5jb208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4sIDx5aXF1QGNpc2NvLmNv
bTxtYWlsdG86eWlxdUBjaXNjby5jb20+PiwgPG15ZXVuZ0BjaXNjby5jb208bWFpbHRvOm15ZXVu
Z0BjaXNjby5jb20+PiwgSmVmZnJleSBaaGFuZyA8enpoYW5nQGp1bmlwZXIubmV0PG1haWx0bzp6
emhhbmdAanVuaXBlci5uZXQ+PiwgPHlpeWFAY2lzY28uY29tPG1haWx0bzp5aXlhQGNpc2NvLmNv
bT4+LCBIZWxlbiBDaGVuIDxpY2hlbkBrdWF0cm90ZWNoLmNvbTxtYWlsdG86aWNoZW5Aa3VhdHJv
dGVjaC5jb20+Pg0KUmVzZW50LURhdGU6IFR1ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiBhdCA3OjE5
IEFNDQoNCkhpLA0KDQpUaGFuayB5b3UgZm9yIHRoaXMgd29yay4gSSBmaW5kIHRoZSBkb2N1bWVu
dCByZWFkYWJsZSBhbmQgdW5kZXJzdGFuZGFibGUuDQoNClNvbWUgY29tbWVudHM6DQoNCkFic3Ry
YWN0Og0KDQotIEluIHRoaXMgc2VudGVuY2UgIkEga2V5IGNoYWluIGlzLi4uIGFsZ29yaXRobSIs
IEkgd291bGQgYWRkICJBIGtleSBjaGFpbiBpcy4uLiBhbGdvcml0aG0gKGF1dGhlbnRpY2F0aW9u
IG9yIGVuY3J5cHRpb24pIi4NCg0KT2sNCg0KDQoNClNlY3Rpb24gMS4gSW50cm9kdWN0aW9uOg0K
DQpJIHdvdWxkIGxpa2UgdG8gaGF2ZSBhbiBleGFtcGxlIG9uIHRoaXMgc3RhdGVtZW50Og0KDQoi
IEluIHNvbWUgYXBwbGljYXRpb25zLCB0aGUgcHJvdG9jb2xzIGRvIG5vdCB1c2UgdGhlIGtleSBj
aGFpbiBlbGVtZW50IGtleQ0KICBkaXJlY3RseSwgYnV0IHJhdGhlciBhIGtleSBkZXJpdmF0aW9u
IGZ1bmN0aW9uIGlzIHVzZWQgdG8gZGVyaXZlIGENCiAgc2hvcnQtbGl2ZWQga2V5IGZyb20gdGhl
IGtleSBjaGFpbiBlbGVtZW50IGtleS4gZS5nLi4uLiIgLS0+IG1heWJlIGRyYWZ0LWJoYXRpYS1r
YXJwLXNob3J0LWxpdmVkLWtleXMtMDA/DQoNCkkgdGhpbmsgVENQLUFPIGlzIGEgYmV0dGVyIGV4
YW1wbGUgc2luY2UgaXQgaXMgYW4gUkZDIGFuZCBleHBsaWNpdGx5IHN1cHBvcnRlZCBieSB0aGUg
bW9kZWwuDQoNCg0KDQpTZWN0aW9uIDEuMS0NCg0KLUkgd291bGQgYWRkIGhlcmUgdGhlIHJlZmVy
ZW5jZSB0byBSRkMgNjAyMCwgc29tZXRoaW5nIGxpa2U6DQoNCiJUaGUgdGVybWlub2xvZ3kgZm9y
IGRlc2NyaWJpbmcgWUFORyBkYXRhIG1vZGVscyBpcyBmb3VuZCBpbiBbUkZDNjAyMF0uDQoNCk9r
Lg0KDQoNCi4uLg0KDQoxLjEuMS4gIFRyZWUgRGlhZ3JhbXMNCg0KICBBIHNpbXBsaWZpZWQgZ3Jh
cGhpY2FsIHJlcHJlc2VudGF0aW9uIG9mIHRoZSBkYXRhIG1vZGVsIGlzIHVzZWQgaW4NCiAgdGhl
IFlBTkcgbW9kdWxlcyBzcGVjaWZpZWQgaW4gdGhpcyBkb2N1bWVudC4gIFRoZSBtZWFuaW5nIG9m
IHRoZQ0KICBzeW1ib2xzIGluIHRoZXNlIGRpYWdyYW1zIGlzIGFzIGZvbGxvd3M6DQoNCiAgICAg
QnJhY2tldHMgIlsiIGFuZCAiXSIgZW5jbG9zZSBsaXN0IGtleXMuDQoNCiAgICAgQWJicmV2aWF0
aW9ucyBiZWZvcmUgZGF0YSBub2RlIG5hbWVzOiAicnciIG1lYW5zIGNvbmZpZ3VyYXRpb24NCiAg
ICAgZGF0YSAocmVhZC13cml0ZSkgYW5kICJybyIgc3RhdGUgZGF0YSAocmVhZC1vbmx5KS4NCg0K
ICAgICBTeW1ib2xzIGFmdGVyIGRhdGEgbm9kZSBuYW1lczogIj8iIG1lYW5zIGFuIG9wdGlvbmFs
IG5vZGUsICIhIg0KICAgICBtZWFucyBhIHByZXNlbmNlIGNvbnRhaW5lciwgYW5kICIqIiBkZW5v
dGVzIGEgbGlzdCBhbmQgbGVhZi1saXN0Lg0KDQogICAgIFBhcmVudGhlc2VzIGVuY2xvc2UgY2hv
aWNlIGFuZCBjYXNlIG5vZGVzLCBhbmQgY2FzZSBub2RlcyBhcmUgYWxzbw0KICAgICBtYXJrZWQg
d2l0aCBhIGNvbG9uICgiOiIpLg0KDQogICAgIEVsbGlwc2lzICgiLi4uIikgc3RhbmRzIGZvciBj
b250ZW50cyBvZiBzdWJ0cmVlcyB0aGF0IGFyZSBub3QNCiAgICAgc2hvd24uIiBzb3VyY2Ugb2Yg
dGhlIHRleHQ6IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12YW5kZXJzdG9rLXJv
bGwtbXBsLXlhbmctMDENCg0KLSBldmVuIHdoZW4gaXQgaXMgcHJldHR5IG9idmlvdXMsIEkgd291
bGQgYWRkIGEgcmVmZXJlbmNlIHRvIHRoZSBrZXkgZGVmaW5pdGlvbiBbUkZDNDk0OSAtIHBhZ2Ug
MTcxXQ0KDQpJ4oCZbGwganVzdCBpbmNsdWRlIHRoZSBub3RhdGlvbiBzZWN0aW9uIHNpbWlsYXIg
dG8gb3RoZXIgWUFORyBkcmFmdHMuDQoNCg0KDQoNClNlY3Rpb24gNToNCg0KICAgICBJdCBpcyBl
bXB0eSwgeW91IG1lbnRpb24gc29tZSByZWxhdGVkIHdvcmsgaW4gc2VjdGlvbiAyLCBidXQgbWF5
YmUgeW91IGNvdWxkIGFkZCBpbiBoZXJlIGEgdHJlZSBkaWFncmFtIHN1Y2ggYXMgdGhlIG9uZSBz
aG93ZWQgaW4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi1z
ZXJ2ZXItbW9kZWwtMDkjc2VjdGlvbi0zDQoNCkFjdHVhbGx5IHRoaXMgbW9kZWwgaXMgbm90IGRl
cGVuZGVudCBvbiBhbnkgb3RoZXJzIChvdGhlciB0aGFuIFlBTkcgdHlwZXMpLiBJdCBpcyB0byBi
ZSByZWZlcmVuY2VkIGJ5IGFueSBtb2R1bGUgcmVxdWlyaW5nIGtleS1jaGFpbiBzZXJ2aWNlcyAo
aS5lLiwgZ2VuZXJhbCBwdXJwb3NlKS4gSeKAmWxsIGFkZCBhIHN0YXRlbWVudCByZWdhcmRpbmcg
dGhlIGFwcGxpY2FiaWxpdHkgdG8gc2VjdGlvbiAyIChQcm9ibGVtIFN0YXRlbWVudCkuDQoNCg0K
U2VjdGlvbiA3DQoNCi1Gb3IgdGhlIFhNTC1SRUdJU1RSWSBJIHdvdWxkIGFkZCBhIHRhYmxlIHdp
dGggc3VnZ2VzdGVkIHZhbHVlcyBmb3IgdGhlIHJlc3BlY3RpdmUgY29sdW1ucyBvZiBucyByZWdp
c3RyeTogSUQsIFVSSSwgRmlsZW5hbWUsIFJlZmVyZW5jZSBbaHR0cDovL3d3dy5pYW5hLm9yZy9h
c3NpZ25tZW50cy94bWwtcmVnaXN0cnkveG1sLXJlZ2lzdHJ5LnhodG1sI25zXQ0KLUZvciBZQU5H
IE1vZHVsZSBOYW1lcyByZWdpc3RyeSwgeW91IGhhdmUgbmFtZSwgbmFtZXNwYWNlLCBwcmVmaXgg
YW5kIHJlZmVyZW5jZSwgb25seSB0aGVyZSBpcyBhIGNvbHVtbiBtaXNzaW5nIHdoaWNoIGlzIG1v
ZHVsZSwgIFtodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3lhbmctcGFyYW1ldGVycy95
YW5nLXBhcmFtZXRlcnMueGh0bWwjeWFuZy1wYXJhbWV0ZXJzLTFdDQoNClRoZXNlIHdvdWxkIGJl
IHRhYmxlcyBvZiAxIDteKSBJIGRvbuKAmXQgc2VlIHRoaXMgYXMgYWRkaW5nIG11Y2ggdmFsdWUu
IEhvd2V2ZXIsIGlmIHlvdSBzZW5kIG1lIHdvcmtpbmcgWE1MLCBJ4oCZZCB1c2UgaXQuDQoNCi0g
SSB3b3VsZCBhZGQgYW4gaW5mb3JtYXRpdmUgcmVmZXJlbmNlIHRvIFJGQzUyMjYuICJHdWlkZWxp
bmVzIGZvciBXcml0aW5nIGFuIElBTkEgQ29uc2lkZXJhdGlvbnMgU2VjdGlvbiBpbiBSRkNzIg0K
DQpJdCBkb2VzbuKAmXQgcmVmZXJlbmNlIFJGQyA1MjI2LiBUaGUgYWxsb2NhdGlvbnMgYXJlIGJh
c2VkIG9uIFJGQyAzNjg4Lg0KDQoNCg0KQWRkaXRpb25hbCBxdWVzdGlvbnM6DQoNCi0gU2hvdWxk
IFJGQyA2NTE4IGJlIG1lbnRpb25lZCBpbiB0aGlzIGRvY3VtZW50PyBsaWtlIHRoZSBDcnlwdG9n
cmFwaGljIEtleXMgTGlmZSBDeWNsZT8NCg0KVGhpcyBkb2N1bWVudCBpcyBhZ2FpbnN0IGtleS1j
aGFpbnMgYW5kIHB1cnBvcnRzIHRoZSBiZW5lZml0cyBvZiBhbiBhdXRvbWF0ZWQga2V5IG1hbmFn
ZW1lbnQgcHJvdG9jb2wuIEkgZG9u4oCZdCBmZWVsIGl0IGlzIGEgZ29vZCByZWZlcmVuY2UgO14p
DQoNCg0KDQotIFdoYXQgYWJvdXQgRUNDPyBTaG91bGQgaXQgYmUgaW5jbHVkZWQgb3IgaXQgaXMg
bm90LXJlbGF0ZWQvb3V0LW9mLXNjb3BlPw0KDQpNeSBpbnRlbnQgd2FzIG5vdCB0byBhZGQgZXZl
cnkgcG9zc2libGUga2V5LWNoYWluIHVzYWdlIGFuZCBJ4oCZdmUgYWxyZWFkeSBpbmNsdWRlZCBh
IGZldyB0aGluZ3MgaW4gdGhlIG1vZGVsIHdoaWNoIGFyZSBub3Qgc3VwcG9ydGVkIGJ5IGFueSB2
ZW5kb3IgKGUuZy4sIFRDUC1BTyBLZXktY2hhaW5zIGFuZCBlbmNyeXB0ZWQgcGFzc3dvcmQgc3Ry
aW5ncykuICBFQ0MgYXNzb2NpYXRlZCBhbGdvcml0aG1zIGNvdWxkIGJlIGFkZGVkIHZpYSBhdWdt
ZW50YXRpb24uDQoNClRoYW5rcywNCkFjZWUNCg0KDQoNCg0KDQpUaGFuayB5b3UsDQoNCkluZXMu
DQoNCg==

--_000_D3EB11E97C410aceeciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <9CFECB154F22C84289A959DBFD1D97D2@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSBJbmVzLCZu
YnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhhbmtzIGZvciB0aGUgcm91dGlu
ZyBkaXJlY3RvcmF0ZSByZXZpZXcuIFNlZSBpbmxpbmUuJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYgc3R5bGU9ImZv
bnQtZmFtaWx5OkNhbGlicmk7IGZvbnQtc2l6ZToxMXB0OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9y
OmJsYWNrOyBCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBu
b25lOyBQQURESU5HLUJPVFRPTTogMGluOyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdI
VDogMGluOyBCT1JERVItVE9QOiAjYjVjNGRmIDFwdCBzb2xpZDsgQk9SREVSLVJJR0hUOiBtZWRp
dW0gbm9uZTsgUEFERElORy1UT1A6IDNwdCI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9s
ZCI+RnJvbTogPC9zcGFuPkluZXMgUm9ibGVzICZsdDs8YSBocmVmPSJtYWlsdG86bWFyaWFpbmVz
cm9ibGVzQGdvb2dsZW1haWwuY29tIj5tYXJpYWluZXNyb2JsZXNAZ29vZ2xlbWFpbC5jb208L2E+
Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+VHVl
c2RheSwgQXVndXN0IDMwLCAyMDE2IGF0IDc6MTkgQU08YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13
ZWlnaHQ6Ym9sZCI+VG86IDwvc3Bhbj5KZWZmIFRhbnRzdXJhICZsdDs8YSBocmVmPSJtYWlsdG86
amVmZnRhbnQuaWV0ZkBnbWFpbC5jb20iPmplZmZ0YW50LmlldGZAZ21haWwuY29tPC9hPiZndDss
IENocmlzIEJvd2VycyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNib3dlcnNAanVuaXBlci5uZXQiPmNi
b3dlcnNAanVuaXBlci5uZXQ8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWll
dGYtcnRnd2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmciPmRyYWZ0LWlldGYtcnRnd2cteWFuZy1r
ZXktY2hhaW5AaWV0Zi5vcmc8L2E+JnF1b3Q7DQogJmx0OzxhIGhyZWY9Im1haWx0bzpkcmFmdC1p
ZXRmLXJ0Z3dnLXlhbmcta2V5LWNoYWluQGlldGYub3JnIj5kcmFmdC1pZXRmLXJ0Z3dnLXlhbmct
a2V5LWNoYWluQGlldGYub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6
Ym9sZCI+Q2M6IDwvc3Bhbj5Kb25hdGhhbiBIYXJkd2ljayAmbHQ7PGEgaHJlZj0ibWFpbHRvOkpv
bmF0aGFuLkhhcmR3aWNrQG1ldGFzd2l0Y2guY29tIj5Kb25hdGhhbi5IYXJkd2lja0BtZXRhc3dp
dGNoLmNvbTwvYT4mZ3Q7LCBSb3V0aW5nIERpcmVjdG9yYXRlICZsdDs8YSBocmVmPSJtYWlsdG86
cnRnLWRpckBpZXRmLm9yZyI+cnRnLWRpckBpZXRmLm9yZzwvYT4mZ3Q7LCBSb3V0aW5nIFdHICZs
dDs8YSBocmVmPSJtYWlsdG86cnRnd2dAaWV0Zi5vcmciPnJ0Z3dnQGlldGYub3JnPC9hPiZndDs8
YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJvdXRp
bmcgRGlyZWN0b3JhdGUgUUEgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXktY2hh
aW48YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+UmVzZW50LUZyb206IDwvc3Bh
bj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmFsaWFzLWJvdW5jZXNAaWV0Zi5vcmciPmFsaWFzLWJvdW5j
ZXNAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5S
ZXNlbnQtVG86IDwvc3Bhbj5BY2VlIExpbmRlbSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFjZWVAY2lz
Y28uY29tIj5hY2VlQGNpc2NvLmNvbTwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnlpcXVA
Y2lzY28uY29tIj55aXF1QGNpc2NvLmNvbTwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm15
ZXVuZ0BjaXNjby5jb20iPm15ZXVuZ0BjaXNjby5jb208L2E+Jmd0OywgSmVmZnJleSBaaGFuZyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOnp6aGFuZ0BqdW5pcGVyLm5ldCI+enpoYW5nQGp1bmlwZXIubmV0
PC9hPiZndDssDQogJmx0OzxhIGhyZWY9Im1haWx0bzp5aXlhQGNpc2NvLmNvbSI+eWl5YUBjaXNj
by5jb208L2E+Jmd0OywgSGVsZW4gQ2hlbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmljaGVuQGt1YXRy
b3RlY2guY29tIj5pY2hlbkBrdWF0cm90ZWNoLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9
ImZvbnQtd2VpZ2h0OmJvbGQiPlJlc2VudC1EYXRlOiA8L3NwYW4+VHVlc2RheSwgQXVndXN0IDMw
LCAyMDE2IGF0IDc6MTkgQU08YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRF
Ui1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7
Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2PkhpLDwvZGl2Pg0KPGRpdj48
YnI+DQo8L2Rpdj4NCjxkaXY+VGhhbmsgeW91IGZvciB0aGlzIHdvcmsuIEkgZmluZCB0aGUgZG9j
dW1lbnQgcmVhZGFibGUgYW5kIHVuZGVyc3RhbmRhYmxlLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+U29tZSBjb21tZW50czo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkFi
c3RyYWN0OjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9ImdtYWls
LUFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+LSBJbiB0aGlz
IHNlbnRlbmNlICZxdW90O0Ega2V5IGNoYWluIGlzLi4uIGFsZ29yaXRobSZxdW90OywgSSB3b3Vs
ZCBhZGQgJnF1b3Q7QSBrZXkgY2hhaW4gaXMuLi4gYWxnb3JpdGhtIChhdXRoZW50aWNhdGlvbiBv
ciBlbmNyeXB0aW9uKSZxdW90Oy4mbmJzcDs8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk9rPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JD
X0JPRFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05f
QkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6
MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5TZWN0aW9uIDEuIEludHJvZHVjdGlvbjo8L2Rpdj4N
CjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3Bh
biIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPkkgd291bGQgbGlrZSB0byBoYXZlIGFu
IGV4YW1wbGUgb24gdGhpcyBzdGF0ZW1lbnQ6PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp
dj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpw
cmUiPjwvc3Bhbj4mcXVvdDsgSW4gc29tZSBhcHBsaWNhdGlvbnMsIHRoZSBwcm90b2NvbHMgZG8g
bm90IHVzZSB0aGUga2V5IGNoYWluIGVsZW1lbnQga2V5PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNz
PSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZu
YnNwOyBkaXJlY3RseSwgYnV0IHJhdGhlciBhIGtleSBkZXJpdmF0aW9uIGZ1bmN0aW9uIGlzIHVz
ZWQgdG8gZGVyaXZlIGE8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9ImdtYWlsLUFwcGxlLXRhYi1z
cGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Jm5ic3A7IHNob3J0LWxpdmVkIGtl
eSBmcm9tIHRoZSBrZXkgY2hhaW4gZWxlbWVudCBrZXkuIGUuZy4uLi4mcXVvdDsgLS0mZ3Q7IG1h
eWJlIGRyYWZ0LWJoYXRpYS1rYXJwLXNob3J0LWxpdmVkLWtleXMtMDA/PC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPGRpdj5JIHRoaW5rIFRDUC1BTyBpcyBhIGJldHRlciBleGFtcGxlIHNpbmNlIGl0IGlzIGFu
IFJGQyBhbmQgZXhwbGljaXRseSBzdXBwb3J0ZWQgYnkgdGhlIG1vZGVsLiZuYnNwOzwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8Ymxv
Y2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJP
UkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAw
IDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9ImdtYWlsLUFwcGxlLXRhYi1zcGFu
IiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+U2VjdGlvbiAxLjEtPC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFiLXNwYW4iIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4tSSB3b3VsZCBhZGQgaGVyZSB0aGUgcmVmZXJl
bmNlIHRvIFJGQyA2MDIwLCBzb21ldGhpbmcgbGlrZTo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNw
YWNlOnByZSI+PC9zcGFuPiZxdW90O1RoZSB0ZXJtaW5vbG9neSBmb3IgZGVzY3JpYmluZyBZQU5H
IGRhdGEgbW9kZWxzIGlzIGZvdW5kIGluIFtSRkM2MDIwXS48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
Pk9rLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JP
RFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxP
Q0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAw
IDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFiLXNwYW4i
IHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4uLi48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRl
LXNwYWNlOnByZSI+PC9zcGFuPjEuMS4xLiZuYnNwOyBUcmVlIERpYWdyYW1zPC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFiLXNwYW4iIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4mbmJzcDsgQSBzaW1wbGlmaWVkIGdyYXBoaWNh
bCByZXByZXNlbnRhdGlvbiBvZiB0aGUgZGF0YSBtb2RlbCBpcyB1c2VkIGluPC9kaXY+DQo8ZGl2
PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnBy
ZSI+PC9zcGFuPiZuYnNwOyB0aGUgWUFORyBtb2R1bGVzIHNwZWNpZmllZCBpbiB0aGlzIGRvY3Vt
ZW50LiZuYnNwOyBUaGUgbWVhbmluZyBvZiB0aGU8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9Imdt
YWlsLUFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Jm5ic3A7
IHN5bWJvbHMgaW4gdGhlc2UgZGlhZ3JhbXMgaXMgYXMgZm9sbG93czo8L2Rpdj4NCjxkaXY+PGJy
Pg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9
IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7QnJhY2tldHMgJnF1
b3Q7WyZxdW90OyBhbmQgJnF1b3Q7XSZxdW90OyBlbmNsb3NlIGxpc3Qga2V5cy48L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIg
c3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7QWJicmV2
aWF0aW9ucyBiZWZvcmUgZGF0YSBub2RlIG5hbWVzOiAmcXVvdDtydyZxdW90OyBtZWFucyBjb25m
aWd1cmF0aW9uPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIg
c3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7ZGF0YSAo
cmVhZC13cml0ZSkgYW5kICZxdW90O3JvJnF1b3Q7IHN0YXRlIGRhdGEgKHJlYWQtb25seSkuPC9k
aXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFi
LXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNw
O1N5bWJvbHMgYWZ0ZXIgZGF0YSBub2RlIG5hbWVzOiAmcXVvdDs/JnF1b3Q7IG1lYW5zIGFuIG9w
dGlvbmFsIG5vZGUsICZxdW90OyEmcXVvdDs8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9ImdtYWls
LUFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Jm5ic3A7ICZu
YnNwOyAmbmJzcDttZWFucyBhIHByZXNlbmNlIGNvbnRhaW5lciwgYW5kICZxdW90OyomcXVvdDsg
ZGVub3RlcyBhIGxpc3QgYW5kIGxlYWYtbGlzdC48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNl
OnByZSI+PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7UGFyZW50aGVzZXMgZW5jbG9zZSBjaG9p
Y2UgYW5kIGNhc2Ugbm9kZXMsIGFuZCBjYXNlIG5vZGVzIGFyZSBhbHNvPC9kaXY+DQo8ZGl2Pjxz
cGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+
PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7bWFya2VkIHdpdGggYSBjb2xvbiAoJnF1b3Q7OiZx
dW90OykuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwt
QXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4mbmJzcDsgJm5i
c3A7ICZuYnNwO0VsbGlwc2lzICgmcXVvdDsuLi4mcXVvdDspIHN0YW5kcyBmb3IgY29udGVudHMg
b2Ygc3VidHJlZXMgdGhhdCBhcmUgbm90PC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1B
cHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPiZuYnNwOyAmbmJz
cDsgJm5ic3A7c2hvd24uJnF1b3Q7IHNvdXJjZSBvZiB0aGUgdGV4dDoNCjxhIGhyZWY9Imh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12YW5kZXJzdG9rLXJvbGwtbXBsLXlhbmctMDEi
Pmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12YW5kZXJzdG9rLXJvbGwtbXBsLXlh
bmctMDE8L2E+PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iZ21h
aWwtQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4tIGV2ZW4g
d2hlbiBpdCBpcyBwcmV0dHkgb2J2aW91cywgSSB3b3VsZCBhZGQgYSByZWZlcmVuY2UgdG8gdGhl
IGtleSBkZWZpbml0aW9uIFtSRkM0OTQ5IC0gcGFnZSAxNzFdPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp
dj5J4oCZbGwganVzdCBpbmNsdWRlIHRoZSBub3RhdGlvbiBzZWN0aW9uIHNpbWlsYXIgdG8gb3Ro
ZXIgWUFORyBkcmFmdHMuJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBp
ZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZU
OiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+U2VjdGlvbiA1OjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
Jm5ic3A7ICZuYnNwOyAmbmJzcDtJdCBpcyBlbXB0eSwgeW91IG1lbnRpb24gc29tZSByZWxhdGVk
IHdvcmsgaW4gc2VjdGlvbiAyLCBidXQgbWF5YmUgeW91IGNvdWxkIGFkZCBpbiBoZXJlIGEgdHJl
ZSBkaWFncmFtIHN1Y2ggYXMgdGhlIG9uZSBzaG93ZWQgaW4NCjxhIGhyZWY9Imh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5ldGNvbmYtc2VydmVyLW1vZGVsLTA5I3NlY3Rp
b24tMyI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRjb25mLXNl
cnZlci1tb2RlbC0wOSNzZWN0aW9uLTM8L2E+Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5B
Y3R1YWxseSB0aGlzIG1vZGVsIGlzIG5vdCBkZXBlbmRlbnQgb24gYW55IG90aGVycyAob3RoZXIg
dGhhbiBZQU5HIHR5cGVzKS4gSXQgaXMgdG8gYmUgcmVmZXJlbmNlZCBieSBhbnkgbW9kdWxlIHJl
cXVpcmluZyBrZXktY2hhaW4gc2VydmljZXMgKGkuZS4sIGdlbmVyYWwgcHVycG9zZSkuIEnigJls
bCBhZGQgYSBzdGF0ZW1lbnQgcmVnYXJkaW5nIHRoZSBhcHBsaWNhYmlsaXR5IHRvIHNlY3Rpb24g
MiAoUHJvYmxlbSBTdGF0ZW1lbnQpLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxz
cGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExP
T0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUg
c29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdiBkaXI9Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5TZWN0aW9uIDc8L2Rpdj4N
CjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJnbWFpbC1BcHBsZS10YWItc3Bh
biIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPi1Gb3IgdGhlIFhNTC1SRUdJU1RSWSBJ
IHdvdWxkIGFkZCBhIHRhYmxlIHdpdGggc3VnZ2VzdGVkIHZhbHVlcyBmb3IgdGhlIHJlc3BlY3Rp
dmUgY29sdW1ucyBvZiBucyByZWdpc3RyeTogSUQsIFVSSSwgRmlsZW5hbWUsIFJlZmVyZW5jZSBb
PGEgaHJlZj0iaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy94bWwtcmVnaXN0cnkveG1s
LXJlZ2lzdHJ5LnhodG1sI25zIj5odHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3htbC1y
ZWdpc3RyeS94bWwtcmVnaXN0cnkueGh0bWwjbnM8L2E+XTwvZGl2Pg0KPGRpdj48c3BhbiBjbGFz
cz0iZ21haWwtQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4t
Rm9yIFlBTkcgTW9kdWxlIE5hbWVzIHJlZ2lzdHJ5LCB5b3UgaGF2ZSBuYW1lLCBuYW1lc3BhY2Us
IHByZWZpeCBhbmQgcmVmZXJlbmNlLCBvbmx5IHRoZXJlIGlzIGEgY29sdW1uIG1pc3Npbmcgd2hp
Y2ggaXMgbW9kdWxlLCAmbmJzcDtbPGEgaHJlZj0iaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25t
ZW50cy95YW5nLXBhcmFtZXRlcnMveWFuZy1wYXJhbWV0ZXJzLnhodG1sI3lhbmctcGFyYW1ldGVy
cy0xIj5odHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3lhbmctcGFyYW1ldGVycy95YW5n
LXBhcmFtZXRlcnMueGh0bWwjeWFuZy1wYXJhbWV0ZXJzLTE8L2E+XTwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4N
CjxkaXY+VGhlc2Ugd291bGQgYmUgdGFibGVzIG9mIDEgO14pIEkgZG9u4oCZdCBzZWUgdGhpcyBh
cyBhZGRpbmcgbXVjaCB2YWx1ZS4gSG93ZXZlciwgaWYgeW91IHNlbmQgbWUgd29ya2luZyBYTUws
IEnigJlkIHVzZSBpdC4mbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0i
T0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJ
QlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQ
QURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGly
PSJsdHIiPg0KPGRpdj48c3BhbiBjbGFzcz0iZ21haWwtQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3
aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4tIEkgd291bGQgYWRkIGFuIGluZm9ybWF0aXZlIHJlZmVy
ZW5jZSB0byBSRkM1MjI2LiAmcXVvdDtHdWlkZWxpbmVzIGZvciBXcml0aW5nIGFuIElBTkEgQ29u
c2lkZXJhdGlvbnMgU2VjdGlvbiBpbiBSRkNzJnF1b3Q7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5J
dCBkb2VzbuKAmXQgcmVmZXJlbmNlIFJGQyA1MjI2LiBUaGUgYWxsb2NhdGlvbnMgYXJlIGJhc2Vk
IG9uIFJGQyAzNjg4LiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJP
TEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklC
VVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBB
RERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9
Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+QWRkaXRp
b25hbCBxdWVzdGlvbnM6PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4tIFNob3VsZCBS
RkMgNjUxOCBiZSBtZW50aW9uZWQgaW4gdGhpcyBkb2N1bWVudD8gbGlrZSB0aGUgQ3J5cHRvZ3Jh
cGhpYyBLZXlzIExpZmUgQ3ljbGU/PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGlzIGRvY3VtZW50
IGlzIGFnYWluc3Qga2V5LWNoYWlucyBhbmQgcHVycG9ydHMgdGhlIGJlbmVmaXRzIG9mIGFuIGF1
dG9tYXRlZCBrZXkgbWFuYWdlbWVudCBwcm90b2NvbC4gSSBkb27igJl0IGZlZWwgaXQgaXMgYSBn
b29kIHJlZmVyZW5jZSA7XikmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBp
ZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FU
VFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlk
OyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYg
ZGlyPSJsdHIiPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pi0g
V2hhdCBhYm91dCBFQ0M/IFNob3VsZCBpdCBiZSBpbmNsdWRlZCBvciBpdCBpcyBub3QtcmVsYXRl
ZC9vdXQtb2Ytc2NvcGU/PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5NeSBpbnRlbnQgd2FzIG5vdCB0
byBhZGQgZXZlcnkgcG9zc2libGUga2V5LWNoYWluIHVzYWdlIGFuZCBJ4oCZdmUgYWxyZWFkeSBp
bmNsdWRlZCBhIGZldyB0aGluZ3MgaW4gdGhlIG1vZGVsIHdoaWNoIGFyZSBub3Qgc3VwcG9ydGVk
IGJ5IGFueSB2ZW5kb3IgKGUuZy4sIFRDUC1BTyBLZXktY2hhaW5zIGFuZCBlbmNyeXB0ZWQgcGFz
c3dvcmQgc3RyaW5ncykuICZuYnNwO0VDQyBhc3NvY2lhdGVkIGFsZ29yaXRobXMgY291bGQgYmUg
YWRkZWQgdmlhIGF1Z21lbnRhdGlvbi4mbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2PlRoYW5rcyw8L2Rpdj4NCjxkaXY+QWNlZSZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0K
PGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxl
PSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjow
IDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGFuayB5b3Us
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JbmVzLjwvZGl2Pg0KPGRpdj48YnI+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_D3EB11E97C410aceeciscocom_--


From nobody Tue Aug 30 09:38:26 2016
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C88B12D149; Tue, 30 Aug 2016 09:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
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 hIpxVHKrJUpa; Tue, 30 Aug 2016 09:38:18 -0700 (PDT)
Received: from mail-ua0-x242.google.com (mail-ua0-x242.google.com [IPv6:2607:f8b0:400c:c08::242]) (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 37E8712D1A6; Tue, 30 Aug 2016 09:38:17 -0700 (PDT)
Received: by mail-ua0-x242.google.com with SMTP id s91so1824153uas.1; Tue, 30 Aug 2016 09:38:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zyp09DE2UbxgO5/GnuLjRibnnyq5xo0Ti1amh1H+TVw=; b=X0T4GRRkCfNdWVxs7yEUWJOAx5cVk2YwKuHoqfgv2IpQN98KkuvPppim/l/0Z2Bwdy FwaYxCc7ra+glys3o4oqF0z5Kwz75H2hhUJ/yTCnTk5QZWz8B1f8VLmX7ikAR69Rks8q +3lGxNc45GuuzA5h7Wu0FyPquE2T+U1de/x4vmBlDajuXkaxYUVRN2yH6cHLvJeQpHfp nUq6BD3EW63mb1Bo2PwVPBs0NyXkGSYuAHlmRs7TsuCszBX+98GZQVYOyakSB9YUldp5 laQ+Exq0+9l9uoAyOo6yhqvqlSefYgIBr8l1Mc48yVtKHW44T7lVuws4T2L7PitU18mq +rYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zyp09DE2UbxgO5/GnuLjRibnnyq5xo0Ti1amh1H+TVw=; b=TCrRWP0JhAhyu09clh33RUZ0LZWX6EteZrJN2GNXvr0dLMsnfv2GvxlZslkZFsGURz jAiTjbKdnze6uVl6jjFa7V3dxFjv0kq0BFJsZbXSMZXjkZUvo/O4lg2wZVM3CscmADxy ofeZRdyfDCWwbyVEqxLZBQ7dc2PM9zhFbmakHYeIRnQCZXmdvzQP9hgy88XUN3GGBr4k iD+7E+1aMXI8/t21L33/A3JnZIoSlajM5FRNSb9PZGBDYNN2ueRxpIGhKXJ9UjfsTIlD cPgeD73uwsZkNSrmk+Er+rs50Kt0dYEA3bdunslxYMxg6tQM+/aM9GhA/4WLDixM7NeW vdlg==
X-Gm-Message-State: AE9vXwM3A/cZ8rm9C2p9nyfymKk4kdfQxDyxYXCfY/MIsUu0iWnXslU+Z0bvTu2UBkgHU2bChqG8iICvPxduyg==
X-Received: by 10.176.68.36 with SMTP id m33mr2826984uam.81.1472575096229; Tue, 30 Aug 2016 09:38:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.36.172 with HTTP; Tue, 30 Aug 2016 09:38:15 -0700 (PDT)
In-Reply-To: <D3EB11E9.7C410%acee@cisco.com>
References: <CAP+sJUfn6n0xR-AugT5=O2kXHj2K0WsPBeXqnP3GQJoD8Md=Xg@mail.gmail.com> <D3EB11E9.7C410%acee@cisco.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
Date: Tue, 30 Aug 2016 19:38:15 +0300
Message-ID: <CAP+sJUenWCxOzA6_bVpNTmRyrRpDcxsr_tFZajkCq=FYHXCiLg@mail.gmail.com>
Subject: Re: Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
To: "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary=94eb2c08c638841522053b4c9b04
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/inovL619NGj1IvicKKn1hYDgrr8>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 16:38:21 -0000

--94eb2c08c638841522053b4c9b04
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Acee,

Thanks for your comments, I understood your points.

Cheers,

Ines.

2016-08-30 19:10 GMT+03:00 Acee Lindem (acee) <acee@cisco.com>:

> Hi Ines,
>
> Thanks for the routing directorate review. See inline.
>
> From: Ines Robles <mariainesrobles@googlemail.com>
> Date: Tuesday, August 30, 2016 at 7:19 AM
> To: Jeff Tantsura <jefftant.ietf@gmail.com>, Chris Bowers <
> cbowers@juniper.net>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <
> draft-ietf-rtgwg-yang-key-chain@ietf.org>
> Cc: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, Routing
> Directorate <rtg-dir@ietf.org>, Routing WG <rtgwg@ietf.org>
> Subject: Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: Acee Lindem <acee@cisco.com>, <yiqu@cisco.com>, <
> myeung@cisco.com>, Jeffrey Zhang <zzhang@juniper.net>, <yiya@cisco.com>,
> Helen Chen <ichen@kuatrotech.com>
> Resent-Date: Tuesday, August 30, 2016 at 7:19 AM
>
> Hi,
>
> Thank you for this work. I find the document readable and understandable.
>
> Some comments:
>
> Abstract:
>
> - In this sentence "A key chain is... algorithm", I would add "A key chai=
n
> is... algorithm (authentication or encryption)".
>
>
> Ok
>
>
>
> Section 1. Introduction:
>
> I would like to have an example on this statement:
>
> " In some applications, the protocols do not use the key chain element ke=
y
>   directly, but rather a key derivation function is used to derive a
>   short-lived key from the key chain element key. e.g...." --> maybe
> draft-bhatia-karp-short-lived-keys-00?
>
>
> I think TCP-AO is a better example since it is an RFC and explicitly
> supported by the model.
>
>
>
> Section 1.1-
>
> -I would add here the reference to RFC 6020, something like:
>
> "The terminology for describing YANG data models is found in [RFC6020].
>
>
> Ok.
>
>
> ...
>
> 1.1.1.  Tree Diagrams
>
>   A simplified graphical representation of the data model is used in
>   the YANG modules specified in this document.  The meaning of the
>   symbols in these diagrams is as follows:
>
>      Brackets "[" and "]" enclose list keys.
>
>      Abbreviations before data node names: "rw" means configuration
>      data (read-write) and "ro" state data (read-only).
>
>      Symbols after data node names: "?" means an optional node, "!"
>      means a presence container, and "*" denotes a list and leaf-list.
>
>      Parentheses enclose choice and case nodes, and case nodes are also
>      marked with a colon (":").
>
>      Ellipsis ("...") stands for contents of subtrees that are not
>      shown." source of the text: https://tools.ietf.org/html/
> draft-vanderstok-roll-mpl-yang-01
>
> - even when it is pretty obvious, I would add a reference to the key
> definition [RFC4949 - page 171]
>
>
> I=E2=80=99ll just include the notation section similar to other YANG draf=
ts.
>
>
>
>
> Section 5:
>
>      It is empty, you mention some related work in section 2, but maybe
> you could add in here a tree diagram such as the one showed in
> https://tools.ietf.org/html/draft-ietf-netconf-server-model-09#section-3
>
>
> Actually this model is not dependent on any others (other than YANG
> types). It is to be referenced by any module requiring key-chain services
> (i.e., general purpose). I=E2=80=99ll add a statement regarding the appli=
cability
> to section 2 (Problem Statement).
>
>
> Section 7
>
> -For the XML-REGISTRY I would add a table with suggested values for the
> respective columns of ns registry: ID, URI, Filename, Reference [
> http://www.iana.org/assignments/xml-registry/xml-registry.xhtml#ns]
> -For YANG Module Names registry, you have name, namespace, prefix and
> reference, only there is a column missing which is module,  [
> http://www.iana.org/assignments/yang-parameters/
> yang-parameters.xhtml#yang-parameters-1]
>
>
> These would be tables of 1 ;^) I don=E2=80=99t see this as adding much va=
lue.
> However, if you send me working XML, I=E2=80=99d use it.
>
> - I would add an informative reference to RFC5226. "Guidelines for Writin=
g
> an IANA Considerations Section in RFCs"
>
>
> It doesn=E2=80=99t reference RFC 5226. The allocations are based on RFC 3=
688.
>
>
>
> Additional questions:
>
> - Should RFC 6518 be mentioned in this document? like the Cryptographic
> Keys Life Cycle?
>
>
> This document is against key-chains and purports the benefits of an
> automated key management protocol. I don=E2=80=99t feel it is a good refe=
rence ;^)
>
>
>
> - What about ECC? Should it be included or it is not-related/out-of-scope=
?
>
>
> My intent was not to add every possible key-chain usage and I=E2=80=99ve =
already
> included a few things in the model which are not supported by any vendor
> (e.g., TCP-AO Key-chains and encrypted password strings).  ECC associated
> algorithms could be added via augmentation.
>
> Thanks,
> Acee
>
>
>
>
>
> Thank you,
>
> Ines.
>
>

--94eb2c08c638841522053b4c9b04
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Acee,<div><br></div><div>Thanks for your comments, I un=
derstood your points.</div><div><br></div><div>Cheers,</div><div><br></div>=
<div>Ines.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2=
016-08-30 19:10 GMT+03:00 Acee Lindem (acee) <span dir=3D"ltr">&lt;<a href=
=3D"mailto:acee@cisco.com" target=3D"_blank">acee@cisco.com</a>&gt;</span>:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi Ines,=C2=A0</div>
<div><br>
</div>
<div>Thanks for the routing directorate review. See inline.=C2=A0</div>
<div><br>
</div>
<span>
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Ines Robles &lt;<a href=3D"ma=
ilto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesrobles@goog=
lemail.<wbr>com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, August 30, 2016 at 7=
:19 AM<br>
<span style=3D"font-weight:bold">To: </span>Jeff Tantsura &lt;<a href=3D"ma=
ilto:jefftant.ietf@gmail.com" target=3D"_blank">jefftant.ietf@gmail.com</a>=
&gt;, Chris Bowers &lt;<a href=3D"mailto:cbowers@juniper.net" target=3D"_bl=
ank">cbowers@juniper.net</a>&gt;, &quot;<a href=3D"mailto:draft-ietf-rtgwg-=
yang-key-chain@ietf.org" target=3D"_blank">draft-ietf-rtgwg-yang-key-<wbr>c=
hain@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org" target=3D"=
_blank">draft-ietf-rtgwg-yang-key-<wbr>chain@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Jonathan Hardwick &lt;<a href=
=3D"mailto:Jonathan.Hardwick@metaswitch.com" target=3D"_blank">Jonathan.Har=
dwick@metaswitch.<wbr>com</a>&gt;, Routing Directorate &lt;<a href=3D"mailt=
o:rtg-dir@ietf.org" target=3D"_blank">rtg-dir@ietf.org</a>&gt;, Routing WG =
&lt;<a href=3D"mailto:rtgwg@ietf.org" target=3D"_blank">rtgwg@ietf.org</a>&=
gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Routing Directorate QA rev=
iew of draft-ietf-rtgwg-yang-key-<wbr>chain<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
alias-bounces@ietf.org" target=3D"_blank">alias-bounces@ietf.org</a>&gt;<br=
>
<span style=3D"font-weight:bold">Resent-To: </span>Acee Lindem &lt;<a href=
=3D"mailto:acee@cisco.com" target=3D"_blank">acee@cisco.com</a>&gt;, &lt;<a=
 href=3D"mailto:yiqu@cisco.com" target=3D"_blank">yiqu@cisco.com</a>&gt;, &=
lt;<a href=3D"mailto:myeung@cisco.com" target=3D"_blank">myeung@cisco.com</=
a>&gt;, Jeffrey Zhang &lt;<a href=3D"mailto:zzhang@juniper.net" target=3D"_=
blank">zzhang@juniper.net</a>&gt;,
 &lt;<a href=3D"mailto:yiya@cisco.com" target=3D"_blank">yiya@cisco.com</a>=
&gt;, Helen Chen &lt;<a href=3D"mailto:ichen@kuatrotech.com" target=3D"_bla=
nk">ichen@kuatrotech.com</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Tuesday, August 30, 20=
16 at 7:19 AM<br>
</div><span class=3D"">
<div><br>
</div>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div>Hi,</div>
<div><br>
</div>
<div>Thank you for this work. I find the document readable and understandab=
le.</div>
<div><br>
</div>
<div>Some comments:</div>
<div><br>
</div>
<div>Abstract:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>- In this sentence &quot;A=
 key chain is... algorithm&quot;, I would add &quot;A key chain is... algor=
ithm (authentication or encryption)&quot;.=C2=A0</div>
</div>
</div>
</div>
</blockquote>
</span></span>
<div><br>
</div>
<div>Ok</div><span class=3D"">
<div><br>
</div>
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div>Section 1. Introduction:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>I would like to have an ex=
ample on this statement:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>&quot; In some application=
s, the protocols do not use the key chain element key</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 directly, but rathe=
r a key derivation function is used to derive a</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 short-lived key fro=
m the key chain element key. e.g....&quot; --&gt; maybe draft-bhatia-karp-s=
hort-lived-<wbr>keys-00?</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>I think TCP-AO is a better example since it is an RFC and expli=
citly supported by the model.=C2=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>Section 1.1-</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>-I would add here the refe=
rence to RFC 6020, something like:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>&quot;The terminology for =
describing YANG data models is found in [RFC6020].</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>Ok.=C2=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>...</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>1.1.1.=C2=A0 Tree Diagrams=
</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 A simplified graphi=
cal representation of the data model is used in</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 the YANG modules sp=
ecified in this document.=C2=A0 The meaning of the</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 symbols in these di=
agrams is as follows:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0Bracke=
ts &quot;[&quot; and &quot;]&quot; enclose list keys.</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0Abbrev=
iations before data node names: &quot;rw&quot; means configuration</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0data (=
read-write) and &quot;ro&quot; state data (read-only).</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0Symbol=
s after data node names: &quot;?&quot; means an optional node, &quot;!&quot=
;</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0means =
a presence container, and &quot;*&quot; denotes a list and leaf-list.</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0Parent=
heses enclose choice and case nodes, and case nodes are also</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0marked=
 with a colon (&quot;:&quot;).</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0Ellips=
is (&quot;...&quot;) stands for contents of subtrees that are not</div>
<div><span style=3D"white-space:pre-wrap"></span>=C2=A0 =C2=A0 =C2=A0shown.=
&quot; source of the text:
<a href=3D"https://tools.ietf.org/html/draft-vanderstok-roll-mpl-yang-01" t=
arget=3D"_blank">https://tools.ietf.org/html/<wbr>draft-vanderstok-roll-mpl=
-<wbr>yang-01</a></div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>- even when it is pretty o=
bvious, I would add a reference to the key definition [RFC4949 - page 171]<=
/div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>I=E2=80=99ll just include the notation section similar to other=
 YANG drafts.=C2=A0</div><span class=3D"">
<div><br>
</div>
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div>Section 5:</div>
<div><br>
</div>
<div>=C2=A0 =C2=A0 =C2=A0It is empty, you mention some related work in sect=
ion 2, but maybe you could add in here a tree diagram such as the one showe=
d in
<a href=3D"https://tools.ietf.org/html/draft-ietf-netconf-server-model-09#s=
ection-3" target=3D"_blank">
https://tools.ietf.org/html/<wbr>draft-ietf-netconf-server-<wbr>model-09#se=
ction-3</a>=C2=A0</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>Actually this model is not dependent on any others (other than =
YANG types). It is to be referenced by any module requiring key-chain servi=
ces (i.e., general purpose). I=E2=80=99ll add a statement regarding the app=
licability to section 2 (Problem Statement).=C2=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div>Section 7</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>-For the XML-REGISTRY I wo=
uld add a table with suggested values for the respective columns of ns regi=
stry: ID, URI, Filename, Reference [<a href=3D"http://www.iana.org/assignme=
nts/xml-registry/xml-registry.xhtml#ns" target=3D"_blank">http://www.iana.o=
rg/<wbr>assignments/xml-registry/xml-<wbr>registry.xhtml#ns</a>]</div>
<div><span style=3D"white-space:pre-wrap"></span>-For YANG Module Names reg=
istry, you have name, namespace, prefix and reference, only there is a colu=
mn missing which is module, =C2=A0[<a href=3D"http://www.iana.org/assignmen=
ts/yang-parameters/yang-parameters.xhtml#yang-parameters-1" target=3D"_blan=
k">http://www.iana.org/<wbr>assignments/yang-parameters/<wbr>yang-parameter=
s.xhtml#yang-<wbr>parameters-1</a>]</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>These would be tables of 1 ;^) I don=E2=80=99t see this as addi=
ng much value. However, if you send me working XML, I=E2=80=99d use it.=C2=
=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><span style=3D"white-space:pre-wrap"></span>- I would add an informati=
ve reference to RFC5226. &quot;Guidelines for Writing an IANA Consideration=
s Section in RFCs&quot;</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>It doesn=E2=80=99t reference RFC 5226. The allocations are base=
d on RFC 3688.=C2=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div>Additional questions:</div>
<div><br>
</div>
<div>- Should RFC 6518 be mentioned in this document? like the Cryptographi=
c Keys Life Cycle?</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>This document is against key-chains and purports the benefits o=
f an automated key management protocol. I don=E2=80=99t feel it is a good r=
eference ;^)=C2=A0</div><span class=3D"">
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div>- What about ECC? Should it be included or it is not-related/out-of-sc=
ope?</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>My intent was not to add every possible key-chain usage and I=
=E2=80=99ve already included a few things in the model which are not suppor=
ted by any vendor (e.g., TCP-AO Key-chains and encrypted password strings).=
=C2=A0 ECC associated algorithms could be added via augmentation.=C2=A0</di=
v>
<div><br>
</div>
<div>Thanks,</div>
<div>Acee=C2=A0</div>
<div><br>
</div>
<div><br>
</div>
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Thank you,</div>
<div><br>
</div>
<div>Ines.</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</div>

</blockquote></div><br></div></div>

--94eb2c08c638841522053b4c9b04--


From nobody Tue Aug 30 09:41:04 2016
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFFDB12D1A5; Tue, 30 Aug 2016 09:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.068
X-Spam-Level: 
X-Spam-Status: No, score=-15.068 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 KwoGa519ao_i; Tue, 30 Aug 2016 09:40:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338CA12D0D8; Tue, 30 Aug 2016 09:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28779; q=dns/txt; s=iport; t=1472575248; x=1473784848; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5nDJL7rTTx2eDId8f2Fgds0MRhdO5vDvZbO2LUMNMzc=; b=jwmc1yvGo6Urdpqenef5KbjrX05wIXNjFEmSrPd16x+NcjmQsBL9UAj+ DGuPn3NAZaNt53+NXrKaG6A5vsTUVWCbrDiDGsTuOoUFUlM4IZSNdwbTI oXkTpLp687RPoho1dO75WTyDWcp9j/9ePuXpAnWlIADei0k5tI5MJt9HA M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMAQAJtsVX/5RdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBgnYzAQEBAQEeV3wHjSeeUowxggEmhXcCHIFCOBQBAgEBAQEBAQFeJ4RhAQE?= =?us-ascii?q?BBCMEUhACAQgOAwMBAhkPAwICAh8RFAkIAgQOBQkQiBEDFw6ubItcDYM9AQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHIp7gkOBZy0JLoI0gloFjiSFZYUTNAGGH4Y+glC?= =?us-ascii?q?BbYgRhVmIP4QJg3gBHjaCDIIkcAGFbH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,257,1470700800";  d="scan'208,217";a="141587344"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2016 16:40:47 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u7UGekH3006150 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 30 Aug 2016 16:40:46 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 30 Aug 2016 12:40:45 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 30 Aug 2016 12:40:45 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ines Robles <mariainesrobles@googlemail.com>
Subject: Re: [RTG-DIR] Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
Thread-Topic: [RTG-DIR] Routing Directorate QA review of draft-ietf-rtgwg-yang-key-chain
Thread-Index: AQHSAt1B6tI3+f6PY0mLmplNCSCyng==
Date: Tue, 30 Aug 2016 16:40:45 +0000
Message-ID: <D3EB2F1F.7C4EB%acee@cisco.com>
References: <CAP+sJUfn6n0xR-AugT5=O2kXHj2K0WsPBeXqnP3GQJoD8Md=Xg@mail.gmail.com> <D3EB11E9.7C410%acee@cisco.com> <CAP+sJUenWCxOzA6_bVpNTmRyrRpDcxsr_tFZajkCq=FYHXCiLg@mail.gmail.com>
In-Reply-To: <CAP+sJUenWCxOzA6_bVpNTmRyrRpDcxsr_tFZajkCq=FYHXCiLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D3EB2F1F7C4EBaceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/5oyu9seu7GUq0QOmpv-F69NXPnY>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 16:40:55 -0000

--_000_D3EB2F1F7C4EBaceeciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSW5lcywNClRoYW5rcyAtIEnigJltIGdvaW5nIHRvIHB1Ymxpc2ggYSB2ZXJzaW9uIG9mIHRo
ZSBkcmFmdCB3aGljaCBhZGRyZXNzZXMgeW91ciBjb21tZW50cy4NCkFjZWUNCg0KRnJvbTogcnRn
LWRpciA8cnRnLWRpci1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpydGctZGlyLWJvdW5jZXNAaWV0
Zi5vcmc+PiBvbiBiZWhhbGYgb2YgSW5lcyBSb2JsZXMgPG1hcmlhaW5lc3JvYmxlc0Bnb29nbGVt
YWlsLmNvbTxtYWlsdG86bWFyaWFpbmVzcm9ibGVzQGdvb2dsZW1haWwuY29tPj4NCkRhdGU6IFR1
ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiBhdCAxMjozOCBQTQ0KVG86IEFjZWUgTGluZGVtIDxhY2Vl
QGNpc2NvLmNvbTxtYWlsdG86YWNlZUBjaXNjby5jb20+Pg0KQ2M6IFJvdXRpbmcgRGlyZWN0b3Jh
dGUgPHJ0Zy1kaXJAaWV0Zi5vcmc8bWFpbHRvOnJ0Zy1kaXJAaWV0Zi5vcmc+PiwgImRyYWZ0LWll
dGYtcnRnd2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtcnRnd2ct
eWFuZy1rZXktY2hhaW5AaWV0Zi5vcmc+IiA8ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFp
bkBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFpbkBpZXRmLm9y
Zz4+LCBDaHJpcyBCb3dlcnMgPGNib3dlcnNAanVuaXBlci5uZXQ8bWFpbHRvOmNib3dlcnNAanVu
aXBlci5uZXQ+PiwgSm9uYXRoYW4gSGFyZHdpY2sgPEpvbmF0aGFuLkhhcmR3aWNrQG1ldGFzd2l0
Y2guY29tPG1haWx0bzpKb25hdGhhbi5IYXJkd2lja0BtZXRhc3dpdGNoLmNvbT4+LCBKZWZmIFRh
bnRzdXJhIDxqZWZmdGFudC5pZXRmQGdtYWlsLmNvbTxtYWlsdG86amVmZnRhbnQuaWV0ZkBnbWFp
bC5jb20+PiwgUm91dGluZyBXRyA8cnRnd2dAaWV0Zi5vcmc8bWFpbHRvOnJ0Z3dnQGlldGYub3Jn
Pj4NClN1YmplY3Q6IFJlOiBbUlRHLURJUl0gUm91dGluZyBEaXJlY3RvcmF0ZSBRQSByZXZpZXcg
b2YgZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFpbg0KDQpIaSBBY2VlLA0KDQpUaGFua3Mg
Zm9yIHlvdXIgY29tbWVudHMsIEkgdW5kZXJzdG9vZCB5b3VyIHBvaW50cy4NCg0KQ2hlZXJzLA0K
DQpJbmVzLg0KDQoyMDE2LTA4LTMwIDE5OjEwIEdNVCswMzowMCBBY2VlIExpbmRlbSAoYWNlZSkg
PGFjZWVAY2lzY28uY29tPG1haWx0bzphY2VlQGNpc2NvLmNvbT4+Og0KSGkgSW5lcywNCg0KVGhh
bmtzIGZvciB0aGUgcm91dGluZyBkaXJlY3RvcmF0ZSByZXZpZXcuIFNlZSBpbmxpbmUuDQoNCkZy
b206IEluZXMgUm9ibGVzIDxtYXJpYWluZXNyb2JsZXNAZ29vZ2xlbWFpbC5jb208bWFpbHRvOm1h
cmlhaW5lc3JvYmxlc0Bnb29nbGVtYWlsLmNvbT4+DQpEYXRlOiBUdWVzZGF5LCBBdWd1c3QgMzAs
IDIwMTYgYXQgNzoxOSBBTQ0KVG86IEplZmYgVGFudHN1cmEgPGplZmZ0YW50LmlldGZAZ21haWwu
Y29tPG1haWx0bzpqZWZmdGFudC5pZXRmQGdtYWlsLmNvbT4+LCBDaHJpcyBCb3dlcnMgPGNib3dl
cnNAanVuaXBlci5uZXQ8bWFpbHRvOmNib3dlcnNAanVuaXBlci5uZXQ+PiwgImRyYWZ0LWlldGYt
cnRnd2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtcnRnd2cteWFu
Zy1rZXktY2hhaW5AaWV0Zi5vcmc+IiA8ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFpbkBp
ZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFpbkBpZXRmLm9yZz4+
DQpDYzogSm9uYXRoYW4gSGFyZHdpY2sgPEpvbmF0aGFuLkhhcmR3aWNrQG1ldGFzd2l0Y2guY29t
PG1haWx0bzpKb25hdGhhbi5IYXJkd2lja0BtZXRhc3dpdGNoLmNvbT4+LCBSb3V0aW5nIERpcmVj
dG9yYXRlIDxydGctZGlyQGlldGYub3JnPG1haWx0bzpydGctZGlyQGlldGYub3JnPj4sIFJvdXRp
bmcgV0cgPHJ0Z3dnQGlldGYub3JnPG1haWx0bzpydGd3Z0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBS
b3V0aW5nIERpcmVjdG9yYXRlIFFBIHJldmlldyBvZiBkcmFmdC1pZXRmLXJ0Z3dnLXlhbmcta2V5
LWNoYWluDQpSZXNlbnQtRnJvbTogPGFsaWFzLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOmFsaWFz
LWJvdW5jZXNAaWV0Zi5vcmc+Pg0KUmVzZW50LVRvOiBBY2VlIExpbmRlbSA8YWNlZUBjaXNjby5j
b208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4sIDx5aXF1QGNpc2NvLmNvbTxtYWlsdG86eWlxdUBj
aXNjby5jb20+PiwgPG15ZXVuZ0BjaXNjby5jb208bWFpbHRvOm15ZXVuZ0BjaXNjby5jb20+Piwg
SmVmZnJleSBaaGFuZyA8enpoYW5nQGp1bmlwZXIubmV0PG1haWx0bzp6emhhbmdAanVuaXBlci5u
ZXQ+PiwgPHlpeWFAY2lzY28uY29tPG1haWx0bzp5aXlhQGNpc2NvLmNvbT4+LCBIZWxlbiBDaGVu
IDxpY2hlbkBrdWF0cm90ZWNoLmNvbTxtYWlsdG86aWNoZW5Aa3VhdHJvdGVjaC5jb20+Pg0KUmVz
ZW50LURhdGU6IFR1ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiBhdCA3OjE5IEFNDQoNCkhpLA0KDQpU
aGFuayB5b3UgZm9yIHRoaXMgd29yay4gSSBmaW5kIHRoZSBkb2N1bWVudCByZWFkYWJsZSBhbmQg
dW5kZXJzdGFuZGFibGUuDQoNClNvbWUgY29tbWVudHM6DQoNCkFic3RyYWN0Og0KDQotIEluIHRo
aXMgc2VudGVuY2UgIkEga2V5IGNoYWluIGlzLi4uIGFsZ29yaXRobSIsIEkgd291bGQgYWRkICJB
IGtleSBjaGFpbiBpcy4uLiBhbGdvcml0aG0gKGF1dGhlbnRpY2F0aW9uIG9yIGVuY3J5cHRpb24p
Ii4NCg0KT2sNCg0KDQoNClNlY3Rpb24gMS4gSW50cm9kdWN0aW9uOg0KDQpJIHdvdWxkIGxpa2Ug
dG8gaGF2ZSBhbiBleGFtcGxlIG9uIHRoaXMgc3RhdGVtZW50Og0KDQoiIEluIHNvbWUgYXBwbGlj
YXRpb25zLCB0aGUgcHJvdG9jb2xzIGRvIG5vdCB1c2UgdGhlIGtleSBjaGFpbiBlbGVtZW50IGtl
eQ0KICBkaXJlY3RseSwgYnV0IHJhdGhlciBhIGtleSBkZXJpdmF0aW9uIGZ1bmN0aW9uIGlzIHVz
ZWQgdG8gZGVyaXZlIGENCiAgc2hvcnQtbGl2ZWQga2V5IGZyb20gdGhlIGtleSBjaGFpbiBlbGVt
ZW50IGtleS4gZS5nLi4uLiIgLS0+IG1heWJlIGRyYWZ0LWJoYXRpYS1rYXJwLXNob3J0LWxpdmVk
LWtleXMtMDA/DQoNCkkgdGhpbmsgVENQLUFPIGlzIGEgYmV0dGVyIGV4YW1wbGUgc2luY2UgaXQg
aXMgYW4gUkZDIGFuZCBleHBsaWNpdGx5IHN1cHBvcnRlZCBieSB0aGUgbW9kZWwuDQoNCg0KDQpT
ZWN0aW9uIDEuMS0NCg0KLUkgd291bGQgYWRkIGhlcmUgdGhlIHJlZmVyZW5jZSB0byBSRkMgNjAy
MCwgc29tZXRoaW5nIGxpa2U6DQoNCiJUaGUgdGVybWlub2xvZ3kgZm9yIGRlc2NyaWJpbmcgWUFO
RyBkYXRhIG1vZGVscyBpcyBmb3VuZCBpbiBbUkZDNjAyMF0uDQoNCk9rLg0KDQoNCi4uLg0KDQox
LjEuMS4gIFRyZWUgRGlhZ3JhbXMNCg0KICBBIHNpbXBsaWZpZWQgZ3JhcGhpY2FsIHJlcHJlc2Vu
dGF0aW9uIG9mIHRoZSBkYXRhIG1vZGVsIGlzIHVzZWQgaW4NCiAgdGhlIFlBTkcgbW9kdWxlcyBz
cGVjaWZpZWQgaW4gdGhpcyBkb2N1bWVudC4gIFRoZSBtZWFuaW5nIG9mIHRoZQ0KICBzeW1ib2xz
IGluIHRoZXNlIGRpYWdyYW1zIGlzIGFzIGZvbGxvd3M6DQoNCiAgICAgQnJhY2tldHMgIlsiIGFu
ZCAiXSIgZW5jbG9zZSBsaXN0IGtleXMuDQoNCiAgICAgQWJicmV2aWF0aW9ucyBiZWZvcmUgZGF0
YSBub2RlIG5hbWVzOiAicnciIG1lYW5zIGNvbmZpZ3VyYXRpb24NCiAgICAgZGF0YSAocmVhZC13
cml0ZSkgYW5kICJybyIgc3RhdGUgZGF0YSAocmVhZC1vbmx5KS4NCg0KICAgICBTeW1ib2xzIGFm
dGVyIGRhdGEgbm9kZSBuYW1lczogIj8iIG1lYW5zIGFuIG9wdGlvbmFsIG5vZGUsICIhIg0KICAg
ICBtZWFucyBhIHByZXNlbmNlIGNvbnRhaW5lciwgYW5kICIqIiBkZW5vdGVzIGEgbGlzdCBhbmQg
bGVhZi1saXN0Lg0KDQogICAgIFBhcmVudGhlc2VzIGVuY2xvc2UgY2hvaWNlIGFuZCBjYXNlIG5v
ZGVzLCBhbmQgY2FzZSBub2RlcyBhcmUgYWxzbw0KICAgICBtYXJrZWQgd2l0aCBhIGNvbG9uICgi
OiIpLg0KDQogICAgIEVsbGlwc2lzICgiLi4uIikgc3RhbmRzIGZvciBjb250ZW50cyBvZiBzdWJ0
cmVlcyB0aGF0IGFyZSBub3QNCiAgICAgc2hvd24uIiBzb3VyY2Ugb2YgdGhlIHRleHQ6IGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12YW5kZXJzdG9rLXJvbGwtbXBsLXlhbmctMDEN
Cg0KLSBldmVuIHdoZW4gaXQgaXMgcHJldHR5IG9idmlvdXMsIEkgd291bGQgYWRkIGEgcmVmZXJl
bmNlIHRvIHRoZSBrZXkgZGVmaW5pdGlvbiBbUkZDNDk0OSAtIHBhZ2UgMTcxXQ0KDQpJ4oCZbGwg
anVzdCBpbmNsdWRlIHRoZSBub3RhdGlvbiBzZWN0aW9uIHNpbWlsYXIgdG8gb3RoZXIgWUFORyBk
cmFmdHMuDQoNCg0KDQoNClNlY3Rpb24gNToNCg0KICAgICBJdCBpcyBlbXB0eSwgeW91IG1lbnRp
b24gc29tZSByZWxhdGVkIHdvcmsgaW4gc2VjdGlvbiAyLCBidXQgbWF5YmUgeW91IGNvdWxkIGFk
ZCBpbiBoZXJlIGEgdHJlZSBkaWFncmFtIHN1Y2ggYXMgdGhlIG9uZSBzaG93ZWQgaW4gaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi1zZXJ2ZXItbW9kZWwtMDkj
c2VjdGlvbi0zDQoNCkFjdHVhbGx5IHRoaXMgbW9kZWwgaXMgbm90IGRlcGVuZGVudCBvbiBhbnkg
b3RoZXJzIChvdGhlciB0aGFuIFlBTkcgdHlwZXMpLiBJdCBpcyB0byBiZSByZWZlcmVuY2VkIGJ5
IGFueSBtb2R1bGUgcmVxdWlyaW5nIGtleS1jaGFpbiBzZXJ2aWNlcyAoaS5lLiwgZ2VuZXJhbCBw
dXJwb3NlKS4gSeKAmWxsIGFkZCBhIHN0YXRlbWVudCByZWdhcmRpbmcgdGhlIGFwcGxpY2FiaWxp
dHkgdG8gc2VjdGlvbiAyIChQcm9ibGVtIFN0YXRlbWVudCkuDQoNCg0KU2VjdGlvbiA3DQoNCi1G
b3IgdGhlIFhNTC1SRUdJU1RSWSBJIHdvdWxkIGFkZCBhIHRhYmxlIHdpdGggc3VnZ2VzdGVkIHZh
bHVlcyBmb3IgdGhlIHJlc3BlY3RpdmUgY29sdW1ucyBvZiBucyByZWdpc3RyeTogSUQsIFVSSSwg
RmlsZW5hbWUsIFJlZmVyZW5jZSBbaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy94bWwt
cmVnaXN0cnkveG1sLXJlZ2lzdHJ5LnhodG1sI25zXQ0KLUZvciBZQU5HIE1vZHVsZSBOYW1lcyBy
ZWdpc3RyeSwgeW91IGhhdmUgbmFtZSwgbmFtZXNwYWNlLCBwcmVmaXggYW5kIHJlZmVyZW5jZSwg
b25seSB0aGVyZSBpcyBhIGNvbHVtbiBtaXNzaW5nIHdoaWNoIGlzIG1vZHVsZSwgIFtodHRwOi8v
d3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3lhbmctcGFyYW1ldGVycy95YW5nLXBhcmFtZXRlcnMu
eGh0bWwjeWFuZy1wYXJhbWV0ZXJzLTFdDQoNClRoZXNlIHdvdWxkIGJlIHRhYmxlcyBvZiAxIDte
KSBJIGRvbuKAmXQgc2VlIHRoaXMgYXMgYWRkaW5nIG11Y2ggdmFsdWUuIEhvd2V2ZXIsIGlmIHlv
dSBzZW5kIG1lIHdvcmtpbmcgWE1MLCBJ4oCZZCB1c2UgaXQuDQoNCi0gSSB3b3VsZCBhZGQgYW4g
aW5mb3JtYXRpdmUgcmVmZXJlbmNlIHRvIFJGQzUyMjYuICJHdWlkZWxpbmVzIGZvciBXcml0aW5n
IGFuIElBTkEgQ29uc2lkZXJhdGlvbnMgU2VjdGlvbiBpbiBSRkNzIg0KDQpJdCBkb2VzbuKAmXQg
cmVmZXJlbmNlIFJGQyA1MjI2LiBUaGUgYWxsb2NhdGlvbnMgYXJlIGJhc2VkIG9uIFJGQyAzNjg4
Lg0KDQoNCg0KQWRkaXRpb25hbCBxdWVzdGlvbnM6DQoNCi0gU2hvdWxkIFJGQyA2NTE4IGJlIG1l
bnRpb25lZCBpbiB0aGlzIGRvY3VtZW50PyBsaWtlIHRoZSBDcnlwdG9ncmFwaGljIEtleXMgTGlm
ZSBDeWNsZT8NCg0KVGhpcyBkb2N1bWVudCBpcyBhZ2FpbnN0IGtleS1jaGFpbnMgYW5kIHB1cnBv
cnRzIHRoZSBiZW5lZml0cyBvZiBhbiBhdXRvbWF0ZWQga2V5IG1hbmFnZW1lbnQgcHJvdG9jb2wu
IEkgZG9u4oCZdCBmZWVsIGl0IGlzIGEgZ29vZCByZWZlcmVuY2UgO14pDQoNCg0KDQotIFdoYXQg
YWJvdXQgRUNDPyBTaG91bGQgaXQgYmUgaW5jbHVkZWQgb3IgaXQgaXMgbm90LXJlbGF0ZWQvb3V0
LW9mLXNjb3BlPw0KDQpNeSBpbnRlbnQgd2FzIG5vdCB0byBhZGQgZXZlcnkgcG9zc2libGUga2V5
LWNoYWluIHVzYWdlIGFuZCBJ4oCZdmUgYWxyZWFkeSBpbmNsdWRlZCBhIGZldyB0aGluZ3MgaW4g
dGhlIG1vZGVsIHdoaWNoIGFyZSBub3Qgc3VwcG9ydGVkIGJ5IGFueSB2ZW5kb3IgKGUuZy4sIFRD
UC1BTyBLZXktY2hhaW5zIGFuZCBlbmNyeXB0ZWQgcGFzc3dvcmQgc3RyaW5ncykuICBFQ0MgYXNz
b2NpYXRlZCBhbGdvcml0aG1zIGNvdWxkIGJlIGFkZGVkIHZpYSBhdWdtZW50YXRpb24uDQoNClRo
YW5rcywNCkFjZWUNCg0KDQoNCg0KDQpUaGFuayB5b3UsDQoNCkluZXMuDQoNCg0K

--_000_D3EB2F1F7C4EBaceeciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <D963140EAD779F4D90A46F912FE2357F@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSBJbmVzLCZu
YnNwOzwvZGl2Pg0KPGRpdj5UaGFua3MgLSBJ4oCZbSBnb2luZyB0byBwdWJsaXNoIGEgdmVyc2lv
biBvZiB0aGUgZHJhZnQgd2hpY2ggYWRkcmVzc2VzIHlvdXIgY29tbWVudHMuJm5ic3A7PC9kaXY+
DQo8ZGl2PkFjZWUmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xL
X1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9u
dC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006
IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAw
aW47IFBBRERJTkctTEVGVDogMGluOyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNi
NWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDog
M3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+cnRnLWRp
ciAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJ0Zy1kaXItYm91bmNlc0BpZXRmLm9yZyI+cnRnLWRpci1i
b3VuY2VzQGlldGYub3JnPC9hPiZndDsgb24gYmVoYWxmIG9mIEluZXMgUm9ibGVzICZsdDs8YSBo
cmVmPSJtYWlsdG86bWFyaWFpbmVzcm9ibGVzQGdvb2dsZW1haWwuY29tIj5tYXJpYWluZXNyb2Js
ZXNAZ29vZ2xlbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpi
b2xkIj5EYXRlOiA8L3NwYW4+VHVlc2RheSwgQXVndXN0IDMwLCAyMDE2IGF0IDEyOjM4IFBNPGJy
Pg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+QWNlZSBMaW5kZW0g
Jmx0OzxhIGhyZWY9Im1haWx0bzphY2VlQGNpc2NvLmNvbSI+YWNlZUBjaXNjby5jb208L2E+Jmd0
Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5DYzogPC9zcGFuPlJvdXRpbmcg
RGlyZWN0b3JhdGUgJmx0OzxhIGhyZWY9Im1haWx0bzpydGctZGlyQGlldGYub3JnIj5ydGctZGly
QGlldGYub3JnPC9hPiZndDssICZxdW90OzxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLXJ0Z3dn
LXlhbmcta2V5LWNoYWluQGlldGYub3JnIj5kcmFmdC1pZXRmLXJ0Z3dnLXlhbmcta2V5LWNoYWlu
QGlldGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtcnRnd2ct
eWFuZy1rZXktY2hhaW5AaWV0Zi5vcmciPmRyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXktY2hhaW5A
aWV0Zi5vcmc8L2E+Jmd0OywNCiBDaHJpcyBCb3dlcnMgJmx0OzxhIGhyZWY9Im1haWx0bzpjYm93
ZXJzQGp1bmlwZXIubmV0Ij5jYm93ZXJzQGp1bmlwZXIubmV0PC9hPiZndDssIEpvbmF0aGFuIEhh
cmR3aWNrICZsdDs8YSBocmVmPSJtYWlsdG86Sm9uYXRoYW4uSGFyZHdpY2tAbWV0YXN3aXRjaC5j
b20iPkpvbmF0aGFuLkhhcmR3aWNrQG1ldGFzd2l0Y2guY29tPC9hPiZndDssIEplZmYgVGFudHN1
cmEgJmx0OzxhIGhyZWY9Im1haWx0bzpqZWZmdGFudC5pZXRmQGdtYWlsLmNvbSI+amVmZnRhbnQu
aWV0ZkBnbWFpbC5jb208L2E+Jmd0OywNCiBSb3V0aW5nIFdHICZsdDs8YSBocmVmPSJtYWlsdG86
cnRnd2dAaWV0Zi5vcmciPnJ0Z3dnQGlldGYub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJlOiBbUlRHLURJUl0gUm91dGluZyBE
aXJlY3RvcmF0ZSBRQSByZXZpZXcgb2YgZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS1jaGFpbjxi
cj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VUTE9P
S19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYgNSBz
b2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJHSU46MCAwIDAgNTsiPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2IGRpcj0ibHRyIj5IaSBBY2VlLA0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhhbmtzIGZv
ciB5b3VyIGNvbW1lbnRzLCBJIHVuZGVyc3Rvb2QgeW91ciBwb2ludHMuPC9kaXY+DQo8ZGl2Pjxi
cj4NCjwvZGl2Pg0KPGRpdj5DaGVlcnMsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5J
bmVzLjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj4NCjxkaXYgY2xhc3M9Imdt
YWlsX3F1b3RlIj4yMDE2LTA4LTMwIDE5OjEwIEdNVCYjNDM7MDM6MDAgQWNlZSBMaW5kZW0gKGFj
ZWUpIDxzcGFuIGRpcj0ibHRyIj4NCiZsdDs8YSBocmVmPSJtYWlsdG86YWNlZUBjaXNjby5jb20i
IHRhcmdldD0iX2JsYW5rIj5hY2VlQGNpc2NvLmNvbTwvYT4mZ3Q7PC9zcGFuPjo8YnI+DQo8Ymxv
Y2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3Jk
ZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgc3R5bGU9Indv
cmQtd3JhcDpicmVhay13b3JkO2NvbG9yOnJnYigwLDAsMCk7Zm9udC1zaXplOjE0cHg7Zm9udC1m
YW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmIj4NCjxkaXY+SGkgSW5lcywmbmJzcDs8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlRoYW5rcyBmb3IgdGhlIHJvdXRpbmcgZGlyZWN0b3JhdGUg
cmV2aWV3LiBTZWUgaW5saW5lLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFu
Pg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTtmb250LXNpemU6MTFwdDt0ZXh0LWFs
aWduOmxlZnQ7Y29sb3I6YmxhY2s7Qk9SREVSLUJPVFRPTTptZWRpdW0gbm9uZTtCT1JERVItTEVG
VDptZWRpdW0gbm9uZTtQQURESU5HLUJPVFRPTTowaW47UEFERElORy1MRUZUOjBpbjtQQURESU5H
LVJJR0hUOjBpbjtCT1JERVItVE9QOiNiNWM0ZGYgMXB0IHNvbGlkO0JPUkRFUi1SSUdIVDptZWRp
dW0gbm9uZTtQQURESU5HLVRPUDozcHQiPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi
PkZyb206IDwvc3Bhbj5JbmVzIFJvYmxlcyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcmlhaW5lc3Jv
Ymxlc0Bnb29nbGVtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1hcmlhaW5lc3JvYmxlc0Bnb29n
bGVtYWlsLjx3YnI+Y29tPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9s
ZCI+RGF0ZTogPC9zcGFuPlR1ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiBhdCA3OjE5IEFNPGJyPg0K
PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+SmVmZiBUYW50c3VyYSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmplZmZ0YW50LmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFu
ayI+amVmZnRhbnQuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OywgQ2hyaXMgQm93ZXJzICZsdDs8YSBo
cmVmPSJtYWlsdG86Y2Jvd2Vyc0BqdW5pcGVyLm5ldCIgdGFyZ2V0PSJfYmxhbmsiPmNib3dlcnNA
anVuaXBlci5uZXQ8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtcnRn
d2cteWFuZy1rZXktY2hhaW5AaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5kcmFmdC1pZXRmLXJ0
Z3dnLXlhbmcta2V5LTx3YnI+Y2hhaW5AaWV0Zi5vcmc8L2E+JnF1b3Q7DQogJmx0OzxhIGhyZWY9
Im1haWx0bzpkcmFmdC1pZXRmLXJ0Z3dnLXlhbmcta2V5LWNoYWluQGlldGYub3JnIiB0YXJnZXQ9
Il9ibGFuayI+ZHJhZnQtaWV0Zi1ydGd3Zy15YW5nLWtleS08d2JyPmNoYWluQGlldGYub3JnPC9h
PiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+Q2M6IDwvc3Bhbj5Kb25h
dGhhbiBIYXJkd2ljayAmbHQ7PGEgaHJlZj0ibWFpbHRvOkpvbmF0aGFuLkhhcmR3aWNrQG1ldGFz
d2l0Y2guY29tIiB0YXJnZXQ9Il9ibGFuayI+Sm9uYXRoYW4uSGFyZHdpY2tAbWV0YXN3aXRjaC48
d2JyPmNvbTwvYT4mZ3Q7LCBSb3V0aW5nIERpcmVjdG9yYXRlICZsdDs8YSBocmVmPSJtYWlsdG86
cnRnLWRpckBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnJ0Zy1kaXJAaWV0Zi5vcmc8L2E+Jmd0
OywNCiBSb3V0aW5nIFdHICZsdDs8YSBocmVmPSJtYWlsdG86cnRnd2dAaWV0Zi5vcmciIHRhcmdl
dD0iX2JsYW5rIj5ydGd3Z0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQt
d2VpZ2h0OmJvbGQiPlN1YmplY3Q6IDwvc3Bhbj5Sb3V0aW5nIERpcmVjdG9yYXRlIFFBIHJldmll
dyBvZiBkcmFmdC1pZXRmLXJ0Z3dnLXlhbmcta2V5LTx3YnI+Y2hhaW48YnI+DQo8c3BhbiBzdHls
ZT0iZm9udC13ZWlnaHQ6Ym9sZCI+UmVzZW50LUZyb206IDwvc3Bhbj4mbHQ7PGEgaHJlZj0ibWFp
bHRvOmFsaWFzLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5hbGlhcy1ib3VuY2Vz
QGlldGYub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+UmVz
ZW50LVRvOiA8L3NwYW4+QWNlZSBMaW5kZW0gJmx0OzxhIGhyZWY9Im1haWx0bzphY2VlQGNpc2Nv
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFjZWVAY2lzY28uY29tPC9hPiZndDssICZsdDs8YSBocmVm
PSJtYWlsdG86eWlxdUBjaXNjby5jb20iIHRhcmdldD0iX2JsYW5rIj55aXF1QGNpc2NvLmNvbTwv
YT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm15ZXVuZ0BjaXNjby5jb20iIHRhcmdldD0iX2Js
YW5rIj5teWV1bmdAY2lzY28uY29tPC9hPiZndDssDQogSmVmZnJleSBaaGFuZyAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnp6aGFuZ0BqdW5pcGVyLm5ldCIgdGFyZ2V0PSJfYmxhbmsiPnp6aGFuZ0BqdW5p
cGVyLm5ldDwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnlpeWFAY2lzY28uY29tIiB0YXJn
ZXQ9Il9ibGFuayI+eWl5YUBjaXNjby5jb208L2E+Jmd0OywgSGVsZW4gQ2hlbiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmljaGVuQGt1YXRyb3RlY2guY29tIiB0YXJnZXQ9Il9ibGFuayI+aWNoZW5Aa3Vh
dHJvdGVjaC5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5S
ZXNlbnQtRGF0ZTogPC9zcGFuPlR1ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiBhdCA3OjE5IEFNPGJy
Pg0KPC9kaXY+DQo8c3BhbiBjbGFzcz0iIj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0iQk9SREVSLUxFRlQ6I2I1YzRkZiA1IHNvbGlkO1BBRERJTkc6MCAwIDAgNTtNQVJH
SU46MCAwIDAgNSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdj5IaSw8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlRoYW5rIHlvdSBmb3IgdGhpcyB3b3JrLiBJIGZp
bmQgdGhlIGRvY3VtZW50IHJlYWRhYmxlIGFuZCB1bmRlcnN0YW5kYWJsZS48L2Rpdj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8ZGl2PlNvbWUgY29tbWVudHM6PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPGRpdj5BYnN0cmFjdDo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUtd3JhcCI+PC9zcGFuPi0gSW4gdGhpcyBzZW50ZW5jZSAmcXVv
dDtBIGtleSBjaGFpbiBpcy4uLiBhbGdvcml0aG0mcXVvdDssIEkgd291bGQgYWRkICZxdW90O0Eg
a2V5IGNoYWluIGlzLi4uIGFsZ29yaXRobSAoYXV0aGVudGljYXRpb24gb3IgZW5jcnlwdGlvbikm
cXVvdDsuJm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L3NwYW4+PC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+T2s8L2Rpdj4NCjxzcGFu
IGNsYXNzPSIiPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3Bhbj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojYjVjNGRmIDUgc29saWQ7UEFERElORzow
IDAgMCA1O01BUkdJTjowIDAgMCA1Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5TZWN0aW9uIDEuIEludHJvZHVjdGlvbjo8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUtd3JhcCI+
PC9zcGFuPkkgd291bGQgbGlrZSB0byBoYXZlIGFuIGV4YW1wbGUgb24gdGhpcyBzdGF0ZW1lbnQ6
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6
cHJlLXdyYXAiPjwvc3Bhbj4mcXVvdDsgSW4gc29tZSBhcHBsaWNhdGlvbnMsIHRoZSBwcm90b2Nv
bHMgZG8gbm90IHVzZSB0aGUga2V5IGNoYWluIGVsZW1lbnQga2V5PC9kaXY+DQo8ZGl2PjxzcGFu
IHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUtd3JhcCI+PC9zcGFuPiZuYnNwOyBkaXJlY3RseSwgYnV0
IHJhdGhlciBhIGtleSBkZXJpdmF0aW9uIGZ1bmN0aW9uIGlzIHVzZWQgdG8gZGVyaXZlIGE8L2Rp
dj4NCjxkaXY+PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+Jm5ic3A7
IHNob3J0LWxpdmVkIGtleSBmcm9tIHRoZSBrZXkgY2hhaW4gZWxlbWVudCBrZXkuIGUuZy4uLi4m
cXVvdDsgLS0mZ3Q7IG1heWJlIGRyYWZ0LWJoYXRpYS1rYXJwLXNob3J0LWxpdmVkLTx3YnI+a2V5
cy0wMD88L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bh
bj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2PkkgdGhpbmsgVENQLUFPIGlzIGEg
YmV0dGVyIGV4YW1wbGUgc2luY2UgaXQgaXMgYW4gUkZDIGFuZCBleHBsaWNpdGx5IHN1cHBvcnRl
ZCBieSB0aGUgbW9kZWwuJm5ic3A7PC9kaXY+DQo8c3BhbiBjbGFzcz0iIj4NCjxkaXY+PGJyPg0K
PC9kaXY+DQo8c3Bhbj4NCjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojYjVjNGRmIDUg
c29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAgMCA1Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRp
diBkaXI9Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+U2VjdGlvbiAxLjEtPC9k
aXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJl
LXdyYXAiPjwvc3Bhbj4tSSB3b3VsZCBhZGQgaGVyZSB0aGUgcmVmZXJlbmNlIHRvIFJGQyA2MDIw
LCBzb21ldGhpbmcgbGlrZTo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUtd3JhcCI+PC9zcGFuPiZxdW90O1RoZSB0ZXJtaW5vbG9neSBm
b3IgZGVzY3JpYmluZyBZQU5HIGRhdGEgbW9kZWxzIGlzIGZvdW5kIGluIFtSRkM2MDIwXS48L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pk9rLiZuYnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9
IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4+DQo8YmxvY2txdW90ZSBzdHlsZT0iQk9SREVS
LUxFRlQ6I2I1YzRkZiA1IHNvbGlkO1BBRERJTkc6MCAwIDAgNTtNQVJHSU46MCAwIDAgNSI+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNw
YW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+Li4uPC9kaXY+DQo8ZGl2Pjxi
cj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bh
bj4xLjEuMS4mbmJzcDsgVHJlZSBEaWFncmFtczwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxk
aXY+PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+Jm5ic3A7IEEgc2lt
cGxpZmllZCBncmFwaGljYWwgcmVwcmVzZW50YXRpb24gb2YgdGhlIGRhdGEgbW9kZWwgaXMgdXNl
ZCBpbjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bh
bj4mbmJzcDsgdGhlIFlBTkcgbW9kdWxlcyBzcGVjaWZpZWQgaW4gdGhpcyBkb2N1bWVudC4mbmJz
cDsgVGhlIG1lYW5pbmcgb2YgdGhlPC9kaXY+DQo8ZGl2PjxzcGFuIHN0eWxlPSJ3aGl0ZS1zcGFj
ZTpwcmUtd3JhcCI+PC9zcGFuPiZuYnNwOyBzeW1ib2xzIGluIHRoZXNlIGRpYWdyYW1zIGlzIGFz
IGZvbGxvd3M6PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hp
dGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNwO0JyYWNrZXRzICZx
dW90O1smcXVvdDsgYW5kICZxdW90O10mcXVvdDsgZW5jbG9zZSBsaXN0IGtleXMuPC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAi
Pjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNwO0FiYnJldmlhdGlvbnMgYmVmb3JlIGRhdGEgbm9k
ZSBuYW1lczogJnF1b3Q7cncmcXVvdDsgbWVhbnMgY29uZmlndXJhdGlvbjwvZGl2Pg0KPGRpdj48
c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZu
YnNwO2RhdGEgKHJlYWQtd3JpdGUpIGFuZCAmcXVvdDtybyZxdW90OyBzdGF0ZSBkYXRhIChyZWFk
LW9ubHkpLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gc3R5bGU9IndoaXRl
LXNwYWNlOnByZS13cmFwIj48L3NwYW4+Jm5ic3A7ICZuYnNwOyAmbmJzcDtTeW1ib2xzIGFmdGVy
IGRhdGEgbm9kZSBuYW1lczogJnF1b3Q7PyZxdW90OyBtZWFucyBhbiBvcHRpb25hbCBub2RlLCAm
cXVvdDshJnF1b3Q7PC9kaXY+DQo8ZGl2PjxzcGFuIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUtd3Jh
cCI+PC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7bWVhbnMgYSBwcmVzZW5jZSBjb250YWluZXIs
IGFuZCAmcXVvdDsqJnF1b3Q7IGRlbm90ZXMgYSBsaXN0IGFuZCBsZWFmLWxpc3QuPC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAi
Pjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNwO1BhcmVudGhlc2VzIGVuY2xvc2UgY2hvaWNlIGFu
ZCBjYXNlIG5vZGVzLCBhbmQgY2FzZSBub2RlcyBhcmUgYWxzbzwvZGl2Pg0KPGRpdj48c3BhbiBz
dHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNwO21h
cmtlZCB3aXRoIGEgY29sb24gKCZxdW90OzomcXVvdDspLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+Jm5ic3A7
ICZuYnNwOyAmbmJzcDtFbGxpcHNpcyAoJnF1b3Q7Li4uJnF1b3Q7KSBzdGFuZHMgZm9yIGNvbnRl
bnRzIG9mIHN1YnRyZWVzIHRoYXQgYXJlIG5vdDwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0id2hp
dGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNwO3Nob3duLiZxdW90
OyBzb3VyY2Ugb2YgdGhlIHRleHQ6IDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC12YW5kZXJzdG9rLXJvbGwtbXBsLXlhbmctMDEiIHRhcmdldD0iX2JsYW5rIj4NCmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC88d2JyPmRyYWZ0LXZhbmRlcnN0b2stcm9sbC1tcGwt
PHdicj55YW5nLTAxPC9hPjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gc3R5
bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+LSBldmVuIHdoZW4gaXQgaXMgcHJldHR5
IG9idmlvdXMsIEkgd291bGQgYWRkIGEgcmVmZXJlbmNlIHRvIHRoZSBrZXkgZGVmaW5pdGlvbiBb
UkZDNDk0OSAtIHBhZ2UgMTcxXTwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9j
a3F1b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+SeKAmWxs
IGp1c3QgaW5jbHVkZSB0aGUgbm90YXRpb24gc2VjdGlvbiBzaW1pbGFyIHRvIG90aGVyIFlBTkcg
ZHJhZnRzLiZuYnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuPg0KPGJsb2NrcXVvdGUgc3R5bGU9IkJPUkRFUi1MRUZU
OiNiNWM0ZGYgNSBzb2xpZDtQQURESU5HOjAgMCAwIDU7TUFSR0lOOjAgMCAwIDUiPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPGRpdj5TZWN0aW9uIDU6PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJz
cDsgJm5ic3A7ICZuYnNwO0l0IGlzIGVtcHR5LCB5b3UgbWVudGlvbiBzb21lIHJlbGF0ZWQgd29y
ayBpbiBzZWN0aW9uIDIsIGJ1dCBtYXliZSB5b3UgY291bGQgYWRkIGluIGhlcmUgYSB0cmVlIGRp
YWdyYW0gc3VjaCBhcyB0aGUgb25lIHNob3dlZCBpbg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi1zZXJ2ZXItbW9kZWwtMDkjc2VjdGlvbi0z
IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvPHdicj5kcmFm
dC1pZXRmLW5ldGNvbmYtc2VydmVyLTx3YnI+bW9kZWwtMDkjc2VjdGlvbi0zPC9hPiZuYnNwOzwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPGRp
dj48YnI+DQo8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+QWN0dWFsbHkgdGhpcyBtb2RlbCBpcyBub3Qg
ZGVwZW5kZW50IG9uIGFueSBvdGhlcnMgKG90aGVyIHRoYW4gWUFORyB0eXBlcykuIEl0IGlzIHRv
IGJlIHJlZmVyZW5jZWQgYnkgYW55IG1vZHVsZSByZXF1aXJpbmcga2V5LWNoYWluIHNlcnZpY2Vz
IChpLmUuLCBnZW5lcmFsIHB1cnBvc2UpLiBJ4oCZbGwgYWRkIGEgc3RhdGVtZW50IHJlZ2FyZGlu
ZyB0aGUgYXBwbGljYWJpbGl0eSB0byBzZWN0aW9uIDIgKFByb2JsZW0gU3RhdGVtZW50KS4mbmJz
cDs8L2Rpdj4NCjxzcGFuIGNsYXNzPSIiPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuPg0KPGJs
b2NrcXVvdGUgc3R5bGU9IkJPUkRFUi1MRUZUOiNiNWM0ZGYgNSBzb2xpZDtQQURESU5HOjAgMCAw
IDU7TUFSR0lOOjAgMCAwIDUiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8ZGl2PlNlY3Rpb24gNzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxk
aXY+PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwIj48L3NwYW4+LUZvciB0aGUgWE1M
LVJFR0lTVFJZIEkgd291bGQgYWRkIGEgdGFibGUgd2l0aCBzdWdnZXN0ZWQgdmFsdWVzIGZvciB0
aGUgcmVzcGVjdGl2ZSBjb2x1bW5zIG9mIG5zIHJlZ2lzdHJ5OiBJRCwgVVJJLCBGaWxlbmFtZSwg
UmVmZXJlbmNlIFs8YSBocmVmPSJodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3htbC1y
ZWdpc3RyeS94bWwtcmVnaXN0cnkueGh0bWwjbnMiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3
LmlhbmEub3JnLzx3YnI+YXNzaWdubWVudHMveG1sLXJlZ2lzdHJ5L3htbC08d2JyPnJlZ2lzdHJ5
LnhodG1sI25zPC9hPl08L2Rpdj4NCjxkaXY+PHNwYW4gc3R5bGU9IndoaXRlLXNwYWNlOnByZS13
cmFwIj48L3NwYW4+LUZvciBZQU5HIE1vZHVsZSBOYW1lcyByZWdpc3RyeSwgeW91IGhhdmUgbmFt
ZSwgbmFtZXNwYWNlLCBwcmVmaXggYW5kIHJlZmVyZW5jZSwgb25seSB0aGVyZSBpcyBhIGNvbHVt
biBtaXNzaW5nIHdoaWNoIGlzIG1vZHVsZSwgJm5ic3A7WzxhIGhyZWY9Imh0dHA6Ly93d3cuaWFu
YS5vcmcvYXNzaWdubWVudHMveWFuZy1wYXJhbWV0ZXJzL3lhbmctcGFyYW1ldGVycy54aHRtbCN5
YW5nLXBhcmFtZXRlcnMtMSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly93d3cuaWFuYS5vcmcvPHdi
cj5hc3NpZ25tZW50cy95YW5nLXBhcmFtZXRlcnMvPHdicj55YW5nLXBhcmFtZXRlcnMueGh0bWwj
eWFuZy08d2JyPnBhcmFtZXRlcnMtMTwvYT5dPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRp
dj5UaGVzZSB3b3VsZCBiZSB0YWJsZXMgb2YgMSA7XikgSSBkb27igJl0IHNlZSB0aGlzIGFzIGFk
ZGluZyBtdWNoIHZhbHVlLiBIb3dldmVyLCBpZiB5b3Ugc2VuZCBtZSB3b3JraW5nIFhNTCwgSeKA
mWQgdXNlIGl0LiZuYnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPHNwYW4+DQo8YmxvY2txdW90ZSBzdHlsZT0iQk9SREVSLUxFRlQ6I2I1YzRkZiA1IHNvbGlk
O1BBRERJTkc6MCAwIDAgNTtNQVJHSU46MCAwIDAgNSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGly
PSJsdHIiPg0KPGRpdj48c3BhbiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlLXdyYXAiPjwvc3Bhbj4t
IEkgd291bGQgYWRkIGFuIGluZm9ybWF0aXZlIHJlZmVyZW5jZSB0byBSRkM1MjI2LiAmcXVvdDtH
dWlkZWxpbmVzIGZvciBXcml0aW5nIGFuIElBTkEgQ29uc2lkZXJhdGlvbnMgU2VjdGlvbiBpbiBS
RkNzJnF1b3Q7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRpdj5JdCBkb2VzbuKAmXQgcmVm
ZXJlbmNlIFJGQyA1MjI2LiBUaGUgYWxsb2NhdGlvbnMgYXJlIGJhc2VkIG9uIFJGQyAzNjg4LiZu
YnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4+DQo8
YmxvY2txdW90ZSBzdHlsZT0iQk9SREVSLUxFRlQ6I2I1YzRkZiA1IHNvbGlkO1BBRERJTkc6MCAw
IDAgNTtNQVJHSU46MCAwIDAgNSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRp
dj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkFkZGl0aW9uYWwgcXVlc3Rp
b25zOjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+LSBTaG91bGQgUkZDIDY1MTggYmUg
bWVudGlvbmVkIGluIHRoaXMgZG9jdW1lbnQ/IGxpa2UgdGhlIENyeXB0b2dyYXBoaWMgS2V5cyBM
aWZlIEN5Y2xlPzwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+VGhpcyBkb2N1bWVudCBp
cyBhZ2FpbnN0IGtleS1jaGFpbnMgYW5kIHB1cnBvcnRzIHRoZSBiZW5lZml0cyBvZiBhbiBhdXRv
bWF0ZWQga2V5IG1hbmFnZW1lbnQgcHJvdG9jb2wuIEkgZG9u4oCZdCBmZWVsIGl0IGlzIGEgZ29v
ZCByZWZlcmVuY2UgO14pJm5ic3A7PC9kaXY+DQo8c3BhbiBjbGFzcz0iIj4NCjxkaXY+PGJyPg0K
PC9kaXY+DQo8c3Bhbj4NCjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojYjVjNGRmIDUg
c29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAgMCA1Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRp
diBkaXI9Imx0ciI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
LSBXaGF0IGFib3V0IEVDQz8gU2hvdWxkIGl0IGJlIGluY2x1ZGVkIG9yIGl0IGlzIG5vdC1yZWxh
dGVkL291dC1vZi1zY29wZT88L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pk15IGludGVu
dCB3YXMgbm90IHRvIGFkZCBldmVyeSBwb3NzaWJsZSBrZXktY2hhaW4gdXNhZ2UgYW5kIEnigJl2
ZSBhbHJlYWR5IGluY2x1ZGVkIGEgZmV3IHRoaW5ncyBpbiB0aGUgbW9kZWwgd2hpY2ggYXJlIG5v
dCBzdXBwb3J0ZWQgYnkgYW55IHZlbmRvciAoZS5nLiwgVENQLUFPIEtleS1jaGFpbnMgYW5kIGVu
Y3J5cHRlZCBwYXNzd29yZCBzdHJpbmdzKS4mbmJzcDsgRUNDIGFzc29jaWF0ZWQgYWxnb3JpdGht
cyBjb3VsZCBiZSBhZGRlZCB2aWEgYXVnbWVudGF0aW9uLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+VGhhbmtzLDwvZGl2Pg0KPGRpdj5BY2VlJm5ic3A7PC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuPg0KPGJsb2NrcXVvdGUgc3R5
bGU9IkJPUkRFUi1MRUZUOiNiNWM0ZGYgNSBzb2xpZDtQQURESU5HOjAgMCAwIDU7TUFSR0lOOjAg
MCAwIDUiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhhbmsgeW91LDwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+SW5lcy48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+PC9kaXY+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_D3EB2F1F7C4EBaceeciscocom_--


From nobody Tue Aug 30 10:33:55 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE40F12D119; Tue, 30 Aug 2016 10:33:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-yang-key-chain-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147257842997.23722.1150433614265179334.idtracker@ietfa.amsl.com>
Date: Tue, 30 Aug 2016 10:33:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/kmoiJe9ELrHupWkt29Q1l4nTdaE>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 17:33:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group of the IETF.

        Title           : Routing Key Chain YANG Data Model
        Authors         : Acee Lindem
                          Yingzhen Qu
                          Derek Yeung
                          Ing-Wher Chen
                          Jeffrey Zhang
                          Yi Yang
	Filename        : draft-ietf-rtgwg-yang-key-chain-08.txt
	Pages           : 22
	Date            : 2016-08-30

Abstract:
   This document describes the key chain YANG data model.  A key chain
   is a list of elements each containing a key, send lifetime, accept
   lifetime, and algorithm (authentication or encryption).  By properly
   overlapping the send and accept lifetimes of multiple key chain
   elements, keys and algorithms may be gracefully updated.  By
   representing them in a YANG data model, key distribution can be
   automated.  Key chains are commonly used for routing protocol
   authentication and other applications.  In some applications, the
   protocols do not use the key chain element key directly, but rather a
   key derivation function is used to derive a short-lived key from the
   key chain element key (e.g., the Master Keys used in the TCP
   Authentication Option.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-yang-key-chain-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-yang-key-chain-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Aug 30 10:46:14 2016
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9BE712D5AE for <rtgwg@ietfa.amsl.com>; Tue, 30 Aug 2016 10:46:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.048
X-Spam-Level: 
X-Spam-Status: No, score=-14.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 enUbZX79DPCE for <rtgwg@ietfa.amsl.com>; Tue, 30 Aug 2016 10:46:11 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C22812B036 for <rtgwg@ietf.org>; Tue, 30 Aug 2016 10:46:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3368; q=dns/txt; s=iport; t=1472579171; x=1473788771; h=from:cc:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=+Zx3kP2JD6alAm5ZFjaCIoiXdQVUP7BZPeJhDm7m7m4=; b=Yeuq6RmcQeXBdTEIYpZzahVZFpRtPx7h5ciTwT5jZRSMXXquncEm8P7L wL/QmncPLjtbYW2nwuN2yUHyNUvPNMD1/cCx0iktBsIcYg21B6D6Vom53 +n5pcPGbF+HZvRIahzaBOvR7ZdlM31tCBvHZqP9DhHFXUWGbaRjuYzNpY M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BSBABCxcVX/4kNJK1cGgEBAQECAQEBA?= =?us-ascii?q?YMpAQEBAQEeV3AMB40nllUElC2CARkLhXkCHAyBNzgUAQIBAQEBAQEBXieEWQk?= =?us-ascii?q?BAQQBAQEgEToLEAIBCBoCJgICAiULFRACEgWFcoJSDq8KjyQBAQEBAQEEAQEBA?= =?us-ascii?q?QEBASCBA4l4hECDAhCCSgWZUAGGH4kOgW1OhA+JDYxIg3gBHjaEMHCFbX8BAQU?=
X-IronPort-AV: E=Sophos;i="5.30,257,1470700800"; d="scan'208";a="316626228"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Aug 2016 17:46:10 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u7UHkAAY027453 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 30 Aug 2016 17:46:10 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 30 Aug 2016 13:46:09 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 30 Aug 2016 13:46:09 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
Subject: Re: I-D Action: draft-ietf-rtgwg-yang-key-chain-08.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-yang-key-chain-08.txt
Thread-Index: AQHSAuTAsYbeyESOv0OU1vGQUeXBZKBhxvoA
Date: Tue, 30 Aug 2016 17:46:09 +0000
Message-ID: <D3EB3E1F.7C522%acee@cisco.com>
References: <147257842997.23722.1150433614265179334.idtracker@ietfa.amsl.com>
In-Reply-To: <147257842997.23722.1150433614265179334.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <65D9EE19A9FB3844A171513997BF735C@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/kRLoDMP5rCknzt-tQ42mT0wOyl4>
Cc: Ines Robles <maria.ines.robles@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 17:46:13 -0000

VGhpcyB2ZXJzaW9uIG9mIHRoZSBkcmFmdCBpbmNsdWRlcyBJbmVzIFJvYmxlc+KAmSBSb3V0aW5n
IERpcmVjdG9yYXRlIFFBDQpSZXZpZXcgY29tbWVudHMuIFRoZXJlIGFyZSBubyBjaGFuZ2VzIHRv
IHRoZSBZQU5HIG1vZGVsLg0KVGhhbmtzLA0KQWNlZQ0KDQpPbiA4LzMwLzE2LCAxOjMzIFBNLCAi
cnRnd2cgb24gYmVoYWxmIG9mIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyINCjxydGd3Zy1ib3Vu
Y2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+IHdyb3Rl
Og0KDQo+DQo+QSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxp
bmUgSW50ZXJuZXQtRHJhZnRzDQo+ZGlyZWN0b3JpZXMuDQo+VGhpcyBkcmFmdCBpcyBhIHdvcmsg
aXRlbSBvZiB0aGUgUm91dGluZyBBcmVhIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+DQo+
ICAgICAgICBUaXRsZSAgICAgICAgICAgOiBSb3V0aW5nIEtleSBDaGFpbiBZQU5HIERhdGEgTW9k
ZWwNCj4gICAgICAgIEF1dGhvcnMgICAgICAgICA6IEFjZWUgTGluZGVtDQo+ICAgICAgICAgICAg
ICAgICAgICAgICAgICBZaW5nemhlbiBRdQ0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgRGVy
ZWsgWWV1bmcNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIEluZy1XaGVyIENoZW4NCj4gICAg
ICAgICAgICAgICAgICAgICAgICAgIEplZmZyZXkgWmhhbmcNCj4gICAgICAgICAgICAgICAgICAg
ICAgICAgIFlpIFlhbmcNCj4JRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi1ydGd3Zy15YW5n
LWtleS1jaGFpbi0wOC50eHQNCj4JUGFnZXMgICAgICAgICAgIDogMjINCj4JRGF0ZSAgICAgICAg
ICAgIDogMjAxNi0wOC0zMA0KPg0KPkFic3RyYWN0Og0KPiAgIFRoaXMgZG9jdW1lbnQgZGVzY3Jp
YmVzIHRoZSBrZXkgY2hhaW4gWUFORyBkYXRhIG1vZGVsLiAgQSBrZXkgY2hhaW4NCj4gICBpcyBh
IGxpc3Qgb2YgZWxlbWVudHMgZWFjaCBjb250YWluaW5nIGEga2V5LCBzZW5kIGxpZmV0aW1lLCBh
Y2NlcHQNCj4gICBsaWZldGltZSwgYW5kIGFsZ29yaXRobSAoYXV0aGVudGljYXRpb24gb3IgZW5j
cnlwdGlvbikuICBCeSBwcm9wZXJseQ0KPiAgIG92ZXJsYXBwaW5nIHRoZSBzZW5kIGFuZCBhY2Nl
cHQgbGlmZXRpbWVzIG9mIG11bHRpcGxlIGtleSBjaGFpbg0KPiAgIGVsZW1lbnRzLCBrZXlzIGFu
ZCBhbGdvcml0aG1zIG1heSBiZSBncmFjZWZ1bGx5IHVwZGF0ZWQuICBCeQ0KPiAgIHJlcHJlc2Vu
dGluZyB0aGVtIGluIGEgWUFORyBkYXRhIG1vZGVsLCBrZXkgZGlzdHJpYnV0aW9uIGNhbiBiZQ0K
PiAgIGF1dG9tYXRlZC4gIEtleSBjaGFpbnMgYXJlIGNvbW1vbmx5IHVzZWQgZm9yIHJvdXRpbmcg
cHJvdG9jb2wNCj4gICBhdXRoZW50aWNhdGlvbiBhbmQgb3RoZXIgYXBwbGljYXRpb25zLiAgSW4g
c29tZSBhcHBsaWNhdGlvbnMsIHRoZQ0KPiAgIHByb3RvY29scyBkbyBub3QgdXNlIHRoZSBrZXkg
Y2hhaW4gZWxlbWVudCBrZXkgZGlyZWN0bHksIGJ1dCByYXRoZXIgYQ0KPiAgIGtleSBkZXJpdmF0
aW9uIGZ1bmN0aW9uIGlzIHVzZWQgdG8gZGVyaXZlIGEgc2hvcnQtbGl2ZWQga2V5IGZyb20gdGhl
DQo+ICAga2V5IGNoYWluIGVsZW1lbnQga2V5IChlLmcuLCB0aGUgTWFzdGVyIEtleXMgdXNlZCBp
biB0aGUgVENQDQo+ICAgQXV0aGVudGljYXRpb24gT3B0aW9uLg0KPg0KPg0KPlRoZSBJRVRGIGRh
dGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPmh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXktY2hhaW4vDQo+DQo+
VGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+aHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXktY2hhaW4tMDgNCj4N
Cj5BIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtcnRnd2cteWFuZy1rZXkt
Y2hhaW4tMDgNCj4NCj4NCj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9m
IG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZg0KPnN1Ym1pc3Npb24NCj51bnRpbCB0aGUgaHRtbGl6
ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPg0K
PkludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoN
Cj5mdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPg0KPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cnRnd2cgbWFpbGluZyBsaXN0DQo+
cnRnd2dAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3J0
Z3dnDQoNCg==


From nobody Tue Aug 30 12:10:33 2016
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885C112D7EF; Tue, 30 Aug 2016 12:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ob3EMQ6xFMvV; Tue, 30 Aug 2016 12:10:31 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (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 EAA8B12B049; Tue, 30 Aug 2016 12:03:59 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id cy9so10200106pac.0; Tue, 30 Aug 2016 12:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :mime-version; bh=qyvgKrYJ3k4MaP+jw+btXdAVhoN5Cbk4Tu61saVQls0=; b=kn3iqcZt4jcMxsH0PaXgVjphrUnT2cju07Ww6Mc03NFAxEGJQ5rlXC0ovAeygqw1AF W+78DZch/kwCYV5KseaYq+VpqD7Y5WSOFJV5d91ABde04o943cZktxl8iRqMyDEFWPVX ClKxH7hvydfPNjH+bCddtFu796/Yp76P/oaHrudcOvQoeh1JfQVwXq42VQk69C1caGYl gcQrdstvCO1Y4iEdAf4+KzCBewRbRzdFF/OTCCqde2o21t0YTAo7VUNMAsZT1ciX3ouF Pyq/PhA7QVVMmmDhctq17mrWoaLu/9hVznT+N43Ukid5L62953+e6oRyqQ0LMeiiSxGQ 0YEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:mime-version; bh=qyvgKrYJ3k4MaP+jw+btXdAVhoN5Cbk4Tu61saVQls0=; b=CLENSCyeaU7T3tIAaHXgjtMMCQpn/2yUqaiR7i5emP8/pqKYfMHWvFfg/6qLw19tJm +JDRRLtcVSqaU5Rrn96rc2h1Vj+VGCwCW/IaSrD0taryPKxo660HEnoGdjXdF7HpE5j6 BS06pR257pPC2sWeP2cgfnpaXFJHT0Fap1KdzXmcwuoy3f294+tptRU5kx00qRbkAz2A BVaRzfW1hBFfVGbPwQguBKDirpSG7fJO2mjLCGE2dKDxd3wDEoNj1aaNaMTw53kH5RkK xm/ZfRAOCpm3VJ5ak5BwYXw2z1sosyRak9R7XEVOJekqlYXlhNvZjJpacbHoTrCZMnkv Sv9w==
X-Gm-Message-State: AE9vXwMYrjrM53UmMYDL9gSAV/bKUweE+U8XQCuXsq4FXlaWKUJp6vfA2vaNFvT4YL60aQ==
X-Received: by 10.66.126.162 with SMTP id mz2mr9137394pab.30.1472583839295; Tue, 30 Aug 2016 12:03:59 -0700 (PDT)
Received: from [192.168.254.3] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id ww14sm59131733pac.34.2016.08.30.12.03.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Aug 2016 12:03:58 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.17.0.160611
Date: Tue, 30 Aug 2016 12:04:29 -0700
Subject: Looking for a shepherd for draft-ietf-rtgwg-yang-key-chain
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>
Message-ID: <BEEE4AE4-6AD8-4D27-AEB6-B24DC5DF1974@gmail.com>
Thread-Topic: Looking for a shepherd for draft-ietf-rtgwg-yang-key-chain
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3555403471_695332527"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/f2bYq3M-j7bnCx-Xo5uZkP3Eiw0>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 19:10:32 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3555403471_695332527
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Dear RTGWG,

=20

As we are getting ready for LC for draft-ietf-rtgwg-yang-key-chain, we are =
looking for a shepherd.

Please let Chris and I know whether you=E2=80=99d be willing to volunteer and cou=
ld start reviewing the document and working with the authors, ideally ASAP.

=20

Thanks! =C2=A0

=20

Cheers,

Jeff & Chris

=20


--B_3555403471_695332527
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Calibri;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:Calibri;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>Dear RTGWG,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt'>As we are getting ready for LC for draft-ietf-rtgwg-yang-key-cha=
in, we are looking for a shepherd.<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt'>Please let Chris and I know whether you&#8217;=
d be willing to volunteer and could start reviewing the document and working=
 with the authors, ideally ASAP.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt'>Thanks! =C2=A0<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Cheers,<o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'=
>Jeff &amp; Chris<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div></body></html>

--B_3555403471_695332527--


