
From nobody Wed Oct  1 06:34:23 2014
Return-Path: <barryleiba@computer.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 374071A0AFE; Wed,  1 Oct 2014 06:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 0ho0VuFOB9RC; Wed,  1 Oct 2014 06:34:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6142F1A0A6B; Wed,  1 Oct 2014 06:34:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Barry Leiba" <barryleiba@computer.org>
To: The IESG <iesg@ietf.org>
Subject: Barry Leiba's No Objection on charter-ietf-rtgwg-04-02: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141001133418.11169.64463.idtracker@ietfa.amsl.com>
Date: Wed, 01 Oct 2014 06:34:18 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/GMKkD3T4lCEquC1n-CBAQIc0oug
Cc: rtg-ads@tools.ietf.org, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 13:34:21 -0000

Barry Leiba has entered the following ballot position for
charter-ietf-rtgwg-04-02: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-rtgwg/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with the comment that "optional" should be removed from the first
sentence.



From nobody Wed Oct  1 06:38:53 2014
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C27D21A8A60; Wed,  1 Oct 2014 06:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level: 
X-Spam-Status: No, score=-15.286 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, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 GQIBpJrCuiQp; Wed,  1 Oct 2014 06:38:39 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 439311ACD2E; Wed,  1 Oct 2014 06:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7338; q=dns/txt; s=iport; t=1412170694; x=1413380294; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=K9hwrPChTEKZWR7gjXPvcPHFZqPUIVvtzVCdr/m1O7g=; b=OAing3TowEhCSWlG0iYoYxhC6imEeK06H4vPPVmHfSQFLtSAQII9K+WJ qT4vcB1I2ttCoJ/rJQqjEfpv0vMhg2AhfSZHPeGgV0zntIxdFKC4S7+pq A7zE3FG6p6O3us2NsaHyyHN3DkWS/PTCsRFaC1zU9gs4uCVnGe0vDA1yR E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAJYCLFStJV2S/2dsb2JhbABggkhGU1kEuVyOb4Fth00CgQsWAXuEAwEBAQR5EAIBCA4DAwECKAchERQJCAIEAQ0FiCoDEQ22cg2HHgEXjXaBThEBPxEHhEsFhiqLQ4Q8hHqCEIFlimCCYYZNg2NsgQ85gQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,632,1406592000";  d="scan'208,217";a="359812079"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-6.cisco.com with ESMTP; 01 Oct 2014 13:38:13 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s91DcD7G022175 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Oct 2014 13:38:13 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Wed, 1 Oct 2014 08:38:13 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Alia Atlas <akatlas@gmail.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
Thread-Topic: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
Thread-Index: AQHP3OOm4pnucdEfDkmZvLTOuJqvPZwa9J+AgABcP4A=
Date: Wed, 1 Oct 2014 13:38:12 +0000
Message-ID: <D0517AB5.3F21%acee@cisco.com>
References: <20140930192026.30652.78430.idtracker@ietfa.amsl.com> <CAG4d1reOvK2NjYu1=JBQEQ+f=ZfQE8L+d=SXEFdixc7OZGp+rQ@mail.gmail.com>
In-Reply-To: <CAG4d1reOvK2NjYu1=JBQEQ+f=ZfQE8L+d=SXEFdixc7OZGp+rQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.196]
Content-Type: multipart/alternative; boundary="_000_D0517AB53F21aceeciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/CsgsA0vzb4mhXuuQOPh3LRIgK1k
Cc: "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 13:38:42 -0000

--_000_D0517AB53F21aceeciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Although I don=92t have a vote, mine would be yes for having these Routing =
YANG models homed in the rtgwg.

From: Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>
Date: Wednesday, October 1, 2014 at 12:08 AM
To: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Cc: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>, "rtgwg-chairs@tools.ietf.org<mailto:rtgwg-chairs@tools.ietf.org>"=
 <rtgwg-chairs@tools.ietf.org<mailto:rtgwg-chairs@tools.ietf.org>>, The IES=
G <iesg@ietf.org<mailto:iesg@ietf.org>>, Routing ADs <rtg-ads@tools.ietf.or=
g<mailto:rtg-ads@tools.ietf.org>>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT=
)

Adrian,

Adding an explicit inclusion for routing-related YANG models not in other w=
orking groups
sounds good to me.  Thanks for the catch and having a helpful extra pointer=
/encouragement.

How does adding it as an explicit larger work item such as:

"The specific larger topics that RTGWG is currently chartered to work on:

 * ....

 * Routing-related YANG models that are not appropriate for other RTG worki=
ng groups.  This
   may include generic routing YANG models.
"

Thoughts?

Alia



On Tue, Sep 30, 2014 at 3:20 PM, Adrian Farrel <adrian@olddog.co.uk<mailto:=
adrian@olddog.co.uk>> wrote:
Adrian Farrel has entered the following ballot position for
charter-ietf-rtgwg-04-02: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-rtgwg/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Fully support this: a good change.

I do not believe this change needs to go for external review.

Nit...
s/an optional venue/a venue/
(There is nothing in "a venue" that implies compulsion)

---

Just noticed something we should add:
RTGWG would be a really good home for routing-related YANG models that
are not specifically covered by other RTG working groups, and for generic
routing YANG models.
Could this be added as a work item?




--_000_D0517AB53F21aceeciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <F769E8C93DAC8543AF93D7D5164956E7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Although I don=92t have a vote, mine would be yes for having these Rou=
ting YANG models homed in the rtgwg.&nbsp;</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Alia Atlas &lt;<a href=3D"mai=
lto:akatlas@gmail.com">akatlas@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, October 1, 2014 at=
 12:08 AM<br>
<span style=3D"font-weight:bold">To: </span>Adrian Farrel &lt;<a href=3D"ma=
ilto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtg=
wg@ietf.org</a>&gt;, &quot;<a href=3D"mailto:rtgwg-chairs@tools.ietf.org">r=
tgwg-chairs@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg-chairs@too=
ls.ietf.org">rtgwg-chairs@tools.ietf.org</a>&gt;,
 The IESG &lt;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;, Routi=
ng ADs &lt;<a href=3D"mailto:rtg-ads@tools.ietf.org">rtg-ads@tools.ietf.org=
</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Adrian Farrel's Yes on=
 charter-ietf-rtgwg-04-02: (with COMMENT)<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir=3D"ltr">Adrian,
<div><br>
</div>
<div>Adding an explicit inclusion for routing-related YANG models not in ot=
her working groups&nbsp;</div>
<div>sounds good to me.&nbsp; Thanks for the catch and having a helpful ext=
ra pointer/encouragement.</div>
<div><br>
</div>
<div>How does adding it as an explicit larger work item such as:</div>
<div><br>
</div>
<div>&quot;<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em=
">The specific larger topics that RTGWG is currently chartered to work on:<=
/span></div>
<div>&nbsp;</div>
<div>&nbsp;* ....&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;* Routing-related YANG models that are not appropriate for other=
 RTG working groups.&nbsp; This</div>
<div>&nbsp; &nbsp;may include generic routing YANG models.</div>
<div>&quot;</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Alia</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Sep 30, 2014 at 3:20 PM, Adrian Farrel <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.=
co.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Adrian Farrel has entered the following ballot position for<br>
charter-ietf-rtgwg-04-02: Yes<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Fully support this: a good change.<br>
<br>
I do not believe this change needs to go for external review.<br>
<br>
Nit...<br>
s/an optional venue/a venue/<br>
(There is nothing in &quot;a venue&quot; that implies compulsion)<br>
<br>
---<br>
<br>
Just noticed something we should add:<br>
RTGWG would be a really good home for routing-related YANG models that<br>
are not specifically covered by other RTG working groups, and for generic<b=
r>
routing YANG models.<br>
Could this be added as a work item?<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_D0517AB53F21aceeciscocom_--


From nobody Wed Oct  1 07:05:22 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEFC1ACDBA; Wed,  1 Oct 2014 07:05:18 -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, SPF_PASS=-0.001] autolearn=ham
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 luKjsf57Nsoi; Wed,  1 Oct 2014 07:05:10 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC5401ACDB7; Wed,  1 Oct 2014 07:05:09 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id b6so145508yha.12 for <multiple recipients>; Wed, 01 Oct 2014 07:05:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0MhCmId11gUEmUvr+T53npIVKAC+cEzYVBLATsdEY8k=; b=LMdp0RyljMMw4xCX0dAqs4FW6BmTbVfVs+uxLo9W21Rek+jOv6m1dWZX8iYdesbGQP DRG5G2MqSCdMZGMQZG6kf2fE25d8qGOGzcQbuAf5kHBlAK9VI68EGD67rJjzocqekL7H lf896DyfvIlZOgcOR/+0bkc3LU7M8w3fqf5MiOPbuxGjVC24C1XJtX43hB3o9hKi8Ebg Tf4/qYNB/japDMmnnS6Ia6yoKvrOB3VzdzU2NiiDdjHVUQtbn9/VqI24JgiLmPY+047q jJ7JgQrlO97O7OtjIf1CejjaaSp76HMl8+7ttWFxGhzgck5bg/sWxiXjm9X3ANgRk7fy c+IA==
MIME-Version: 1.0
X-Received: by 10.236.41.100 with SMTP id g64mr79926851yhb.60.1412172308890; Wed, 01 Oct 2014 07:05:08 -0700 (PDT)
Received: by 10.170.110.72 with HTTP; Wed, 1 Oct 2014 07:05:08 -0700 (PDT)
In-Reply-To: <D0517AB5.3F21%acee@cisco.com>
References: <20140930192026.30652.78430.idtracker@ietfa.amsl.com> <CAG4d1reOvK2NjYu1=JBQEQ+f=ZfQE8L+d=SXEFdixc7OZGp+rQ@mail.gmail.com> <D0517AB5.3F21%acee@cisco.com>
Date: Wed, 1 Oct 2014 10:05:08 -0400
Message-ID: <CAG4d1rfDm=2icGU7vvdwVZZyX0w8G_F5sw3tE-dn9Ddjj8zLNA@mail.gmail.com>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary=089e0160b3d2d54bac05045cfca9
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/ielKuxABePus9vT-Sh8U0luBA1g
Cc: Adrian Farrel <adrian@olddog.co.uk>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 14:05:18 -0000

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

Acee,

Your opinion, perspective, and willingness to review and work on the drafts
is always welcome.

Regards,
Alia

On Wed, Oct 1, 2014 at 9:38 AM, Acee Lindem (acee) <acee@cisco.com> wrote:

>  Although I don=E2=80=99t have a vote, mine would be yes for having these=
 Routing
> YANG models homed in the rtgwg.
>
>   From: Alia Atlas <akatlas@gmail.com>
> Date: Wednesday, October 1, 2014 at 12:08 AM
> To: Adrian Farrel <adrian@olddog.co.uk>
> Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <
> rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, Routing ADs <
> rtg-ads@tools.ietf.org>
> Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with
> COMMENT)
>
>   Adrian,
>
>  Adding an explicit inclusion for routing-related YANG models not in
> other working groups
> sounds good to me.  Thanks for the catch and having a helpful extra
> pointer/encouragement.
>
>  How does adding it as an explicit larger work item such as:
>
>  "The specific larger topics that RTGWG is currently chartered to work on=
:
>
>  * ....
>
>  * Routing-related YANG models that are not appropriate for other RTG
> working groups.  This
>    may include generic routing YANG models.
> "
>
>  Thoughts?
>
>  Alia
>
>
>
> On Tue, Sep 30, 2014 at 3:20 PM, Adrian Farrel <adrian@olddog.co.uk>
> wrote:
>
>> Adrian Farrel has entered the following ballot position for
>> charter-ietf-rtgwg-04-02: Yes
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Fully support this: a good change.
>>
>> I do not believe this change needs to go for external review.
>>
>> Nit...
>> s/an optional venue/a venue/
>> (There is nothing in "a venue" that implies compulsion)
>>
>> ---
>>
>> Just noticed something we should add:
>> RTGWG would be a really good home for routing-related YANG models that
>> are not specifically covered by other RTG working groups, and for generi=
c
>> routing YANG models.
>> Could this be added as a work item?
>>
>>
>>
>

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

<div dir=3D"ltr">Acee,<div><br></div><div>Your opinion, perspective, and wi=
llingness to review and work on the drafts is always welcome.</div><div><br=
></div><div>Regards,</div><div>Alia</div></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Wed, Oct 1, 2014 at 9:38 AM, Acee Lindem (=
acee) <span dir=3D"ltr">&lt;<a href=3D"mailto:acee@cisco.com" target=3D"_bl=
ank">acee@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left: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>Although I don=E2=80=99t have a vote, mine would be yes for having the=
se Routing YANG models homed in the rtgwg.=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>Alia Atlas &lt;<a href=3D"mai=
lto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, October 1, 2014 at=
 12:08 AM<br>
<span style=3D"font-weight:bold">To: </span>Adrian Farrel &lt;<a href=3D"ma=
ilto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:rtgwg@i=
etf.org" target=3D"_blank">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:r=
tgwg@ietf.org" target=3D"_blank">rtgwg@ietf.org</a>&gt;, &quot;<a href=3D"m=
ailto:rtgwg-chairs@tools.ietf.org" target=3D"_blank">rtgwg-chairs@tools.iet=
f.org</a>&quot; &lt;<a href=3D"mailto:rtgwg-chairs@tools.ietf.org" target=
=3D"_blank">rtgwg-chairs@tools.ietf.org</a>&gt;,
 The IESG &lt;<a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.=
org</a>&gt;, Routing ADs &lt;<a href=3D"mailto:rtg-ads@tools.ietf.org" targ=
et=3D"_blank">rtg-ads@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Adrian Farrel&#39;s Ye=
s on charter-ietf-rtgwg-04-02: (with COMMENT)<br>
</div><div><div class=3D"h5">
<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">Adrian,
<div><br>
</div>
<div>Adding an explicit inclusion for routing-related YANG models not in ot=
her working groups=C2=A0</div>
<div>sounds good to me.=C2=A0 Thanks for the catch and having a helpful ext=
ra pointer/encouragement.</div>
<div><br>
</div>
<div>How does adding it as an explicit larger work item such as:</div>
<div><br>
</div>
<div>&quot;<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em=
">The specific larger topics that RTGWG is currently chartered to work on:<=
/span></div>
<div>=C2=A0</div>
<div>=C2=A0* ....=C2=A0</div>
<div>=C2=A0</div>
<div>=C2=A0* Routing-related YANG models that are not appropriate for other=
 RTG working groups.=C2=A0 This</div>
<div>=C2=A0 =C2=A0may include generic routing YANG models.</div>
<div>&quot;</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Alia</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Sep 30, 2014 at 3:20 PM, Adrian Farrel <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.=
co.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Adrian Farrel has entered the following ballot position for<br>
charter-ietf-rtgwg-04-02: Yes<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Fully support this: a good change.<br>
<br>
I do not believe this change needs to go for external review.<br>
<br>
Nit...<br>
s/an optional venue/a venue/<br>
(There is nothing in &quot;a venue&quot; that implies compulsion)<br>
<br>
---<br>
<br>
Just noticed something we should add:<br>
RTGWG would be a really good home for routing-related YANG models that<br>
are not specifically covered by other RTG working groups, and for generic<b=
r>
routing YANG models.<br>
Could this be added as a work item?<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div></div></span>
</div>

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

--089e0160b3d2d54bac05045cfca9--


From nobody Wed Oct  1 08:09:10 2014
Return-Path: <Bhuvanesh.Rajput@tatacommunications.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3A71A1A26 for <rtgwg@ietfa.amsl.com>; Wed,  1 Oct 2014 08:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 3utAVsLATvOC for <rtgwg@ietfa.amsl.com>; Wed,  1 Oct 2014 08:09:05 -0700 (PDT)
Received: from vmx6.tatacommunications.com (vmx6.tatacommunications.com [115.114.148.226]) by ietfa.amsl.com (Postfix) with ESMTP id 067611A1A12 for <rtgwg@ietf.org>; Wed,  1 Oct 2014 08:09:02 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.04,632,1406572200"; d="scan'208,217"; a="69018672"
Received: from inp44vcas02.vsnl.co.in ([121.244.253.17]) by mx6-2.tatacommunications.com with ESMTP; 01 Oct 2014 20:39:00 +0530
Received: from INP44VDAG02.vsnl.co.in ([fe80::79c8:e95b:2f43:3d90]) by inp44vcas02.vsnl.co.in ([fe80::98c5:cb52:8d40:d09b%12]) with mapi id 14.03.0181.006; Wed, 1 Oct 2014 20:39:01 +0530
From: Bhuvanesh Rajput <Bhuvanesh.Rajput@tatacommunications.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Requesting Comments about the Draft : draft-arumuganainar-rtgwg-dps-requirements-00.txt
Thread-Topic: Requesting Comments about the Draft : draft-arumuganainar-rtgwg-dps-requirements-00.txt
Thread-Index: Ac/dhnJovWcCHIN6RCm1QoJ9CW7aiQ==
Date: Wed, 1 Oct 2014 15:09:00 +0000
Message-ID: <E3DFEE681C8ABF4A8AC076EFF3DDD6DEDBF1169A@inp44vdag02.vsnl.co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [121.244.253.8]
Content-Type: multipart/alternative; boundary="_000_E3DFEE681C8ABF4A8AC076EFF3DDD6DEDBF1169Ainp44vdag02vsnl_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Wg35CodLFAOIy6lYwEE1vNQQayg
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 15:09:08 -0000

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

Hi,

Dynamic path selections draft is well written to have application based fle=
xibility in the routing.

Seek clarification on following


-          Application based traffic offload/routing requirement most often=
 comes from enterprise segment, never seen from service providers.
Since BGP is proposed in the draft to achieve application based routing but=
 BGP is most often used between Autonomous systems (between Service provide=
rs and Enterprise and Service Providers), Why widely accepted and deployed =
IGPs (OSPF and EIGRP) cannot work to achieve proposed functionality? If IGP=
s are supported to have application based routing it will great value add f=
or large Enterprises segment without any major change in existing routing.


-          Draft proposes static configuration to define application profil=
e, how to achieve the routing for the applications dynamic in nature and us=
e dynamic port numbers etc. ?


Regards
Bhuvanesh Rajput


--_000_E3DFEE681C8ABF4A8AC076EFF3DDD6DEDBF1169Ainp44vdag02vsnl_
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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	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;}
/* List Definitions */
@list l0
	{mso-list-id:883294613;
	mso-list-type:hybrid;
	mso-list-template-ids:-1193274414 1385457650 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1716538497;
	mso-list-type:hybrid;
	mso-list-template-ids:735073454 1385457650 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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"#0563C1" vlink=3D"#954F72">
<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">Dynamic path selections draft is well written to hav=
e application based flexibility in the routing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Seek clarification on following <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Application based traffic offload/routing requireme=
nt most often comes from enterprise segment, never seen from service provid=
ers.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Since BGP is proposed in =
the draft to achieve application based routing but BGP is most often used b=
etween Autonomous systems (between Service providers and Enterprise and Ser=
vice Providers), Why widely accepted
 and deployed IGPs (OSPF and EIGRP) cannot work to achieve proposed functio=
nality? If IGPs are supported to have application based routing it will gre=
at value add for large Enterprises segment without any major change in exis=
ting routing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Draft proposes static configuration to define appli=
cation profile, how to achieve the routing for the applications dynamic in =
nature and use dynamic port numbers etc. ?<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">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Bhuvanesh Rajput<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_E3DFEE681C8ABF4A8AC076EFF3DDD6DEDBF1169Ainp44vdag02vsnl_--


From nobody Wed Oct  1 08:13:43 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4FD1ACE4F; Wed,  1 Oct 2014 08:13:37 -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, SPF_PASS=-0.001] autolearn=ham
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 5mkXInkRCW9Q; Wed,  1 Oct 2014 08:13:36 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1628B1A1A76; Wed,  1 Oct 2014 08:13:36 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id f10so193355yha.41 for <multiple recipients>; Wed, 01 Oct 2014 08:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5U4t0exDBib+BcfO+nhh3yUITgmplRBuOCEsca00nm0=; b=H7YHkexHi79Wcs/FRA+VtmZLrxPpDTDWp+XmvDmor/Bo5kywL3gGzx8YPGzUZ2rG/i Bi1sNDI5O1LqSaDVcBBO7QBCud9qUEKaMk5K8GZi3KDyZQ4B+j/atC6VkLub/wiqaR7w R4C3ehQsS7vl1xKdCNWGa1UENAHt89fcI9Z7gEQZNmxlvprAQSx3qP7kSoxvfoih0HgH MhimSs8p7U+Iy2u/qC33vV7wD0cpC0AVe0WQG6PJLxPJds4p6RhEIpXHvQQK3RSdEiOr 4EgYGuZkGXIa1M7MlYD0DRhrz8e+Y4yFc5j1J6FqGtFjF790PfiH0nP9/qEQt2ePrQre iOTw==
MIME-Version: 1.0
X-Received: by 10.236.97.38 with SMTP id s26mr20258932yhf.107.1412176414428; Wed, 01 Oct 2014 08:13:34 -0700 (PDT)
Received: by 10.170.110.72 with HTTP; Wed, 1 Oct 2014 08:13:34 -0700 (PDT)
In-Reply-To: <20141001133418.11169.64463.idtracker@ietfa.amsl.com>
References: <20141001133418.11169.64463.idtracker@ietfa.amsl.com>
Date: Wed, 1 Oct 2014 11:13:34 -0400
Message-ID: <CAG4d1rfyR1WrUGCyiJxT25Mf4+6ZjtdKNj=67+m887hPw8A6NA@mail.gmail.com>
Subject: Re: Barry Leiba's No Objection on charter-ietf-rtgwg-04-02: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11c1ca848ad5e605045df1b0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/mJexrCpIu2DyODnct3GqRk_TLl8
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 15:13:38 -0000

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

On Wed, Oct 1, 2014 at 9:34 AM, Barry Leiba <barryleiba@computer.org> wrote:

> Barry Leiba has entered the following ballot position for
> charter-ietf-rtgwg-04-02: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I agree with the comment that "optional" should be removed from the first
> sentence.
>

Sure.  It was put in to make it clear that RTGWG isn't a mandatory hurdle
for
work that is large/organized/ready for a BoF.

Alia


>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Oct 1, 2014 at 9:34 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.org</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Barry Leiba has entere=
d the following ballot position for<br>
charter-ietf-rtgwg-04-02: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
I agree with the comment that &quot;optional&quot; should be removed from t=
he first<br>
sentence.<br></blockquote><div><br></div><div>Sure.=C2=A0 It was put in to =
make it clear that RTGWG isn&#39;t a mandatory hurdle for</div><div>work th=
at is large/organized/ready for a BoF.</div><div><br></div><div>Alia</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
_______________________________________________<br>
rtgwg mailing list<br>
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/rtgwg</a><br>
</blockquote></div><br></div></div>

--001a11c1ca848ad5e605045df1b0--


From nobody Wed Oct  1 14:53:29 2014
Return-Path: <arun.arumuganainar@tatacommunications.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5361A87C4 for <rtgwg@ietfa.amsl.com>; Wed,  1 Oct 2014 14:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 4pcXJGGwG92P for <rtgwg@ietfa.amsl.com>; Wed,  1 Oct 2014 14:53:24 -0700 (PDT)
Received: from vmx3.tatacommunications.com (vmx3.tatacommunications.com [66.198.167.208]) by ietfa.amsl.com (Postfix) with ESMTP id 13F4C1A87AF for <rtgwg@ietf.org>; Wed,  1 Oct 2014 14:53:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,635,1406606400"; d="scan'208";a="48716495"
Received: from unknown (HELO wv1-cas-01.vsnl.co.in) ([64.86.157.137]) by mx3-2.tatacommunications.com with ESMTP; 01 Oct 2014 17:53:23 -0400
Received: from USWV1VCAS01.vsnl.co.in (64.86.157.177) by wv1-cas-01.vsnl.co.in (64.86.157.137) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 1 Oct 2014 17:53:23 -0400
Received: from USWV1VDAG02.vsnl.co.in ([fe80::7c6a:fd71:7022:40b6]) by uswv1vcas01.vsnl.co.in ([fe80::6521:bbe2:f2e4:7b9b%11]) with mapi id 14.03.0181.006; Wed, 1 Oct 2014 17:53:23 -0400
From: Arun Arumuganainar <arun.arumuganainar@tatacommunications.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Requesting Comments about the Draft :draft-arumuganainar-rtgwg-dps-requirements-00.txt 
Thread-Topic: Requesting Comments about the Draft :draft-arumuganainar-rtgwg-dps-requirements-00.txt 
Thread-Index: Ac/dvHPg78AW1mHDT4O4dIRI+LcQOg==
Date: Wed, 1 Oct 2014 21:53:23 +0000
Message-ID: <8E0F17CF07213C4882E85670E17849E1A04949FB@uswv1vdag02.vsnl.co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.86.157.8]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/R7mH1MKvlKFdIPwYMEeDlj9tSrw
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 01 Oct 2014 21:53:28 -0000

Hi Bhuvanesh ,

Thanks very much  for taking time to read through the draft.

-          Application based traffic offload/routing requirement most often=
 comes from enterprise segment, never seen from service providers.
Since BGP is proposed in the draft to achieve application based routing but=
 BGP is most often used between Autonomous systems (between Service provide=
rs and Enterprise and Service Providers), Why widely accepted and deployed =
IGPs (OSPF and EIGRP) cannot work to achieve proposed functionality? If IGP=
s are supported to have application based routing it will great value add f=
or large Enterprises segment without any major change in existing routing.

<<ARUN>>

My  draft focus on Enterprise networks that are globally spread across . Ty=
pically they will go for MPLS or other forms of VPN technology with choice =
of Last miles.  Invariably bottle neck or congestion will happen on the las=
t mile and not the SP's core. Hence the draft focus on managing congestion =
on the last miles. This we do by offloading applications on to other availa=
ble Paths to the SP's VPN cloud. Just to clarify , the draft does not care =
about load sharing with in LAN or Campus network. The Focus really on globa=
l Wan networks. =20

BGP is the widely used protocol on the wan network (between the CE and PE d=
evices) .

Again , My draft does not suggest BGP  for signalling. However I have menti=
oned BGP is used in the current implementations. In the current implementat=
ion of BGP available in market , there are enough flexibility to pass on si=
gnalling information directly to forwarding plane. That's was reason curren=
t implementations are done through BGP.

Infact I have also posted another draft (draft-arumuganainar-rtgwg-dps-l4-p=
pn-00)  exclusively on signalling . Here I have proposed to use the signall=
ing to be done during TCP connection establishment phase( 3 way handshake )=
. When implemented this could result in more dynamic offloading then we can=
 achieve today.=20

To summarise , BGP is one way to do signalling for DPS. But other ways coul=
d be developed as well. I am always open for suggestion . I would be very h=
appy if we could refine the signalling techniques.

<<ARUN>>

-          Draft proposes static configuration to define application profil=
e, how to achieve the routing for the applications dynamic in nature and us=
e dynamic port numbers etc. ?
=20
<<ARUN>>

 Again I am from SP background with very little scope for modifying code an=
d trying out new things. Our implementations are constrained  by limitation=
 of products currently available in the market . Current implementation all=
ow only static definition.  But the proposed frame work allows more dynamic=
 path selection as well ( Pls. refer to use cases draft - draft-arumuganain=
ar-rtgwg-dps-use-cases-00  ; where dynamic scenarios are discussed ).

However most of use cases  would require more development to be done .  Tha=
t was one of the reason I have come to IETF. Requirements Draft is more of =
a problem statement than proposed solution :-).

<<ARUN>>

Pls. let me know if you have any further clarifications.

Thanks and Regards
Arun


Arun Arumuganainar
CCIE#16918 ( R&S and SP )    =20
Technical Design Authority=20
Advanced Solution Delivery
Tata Communications Limited
Direct +44 207 029 9513=A0=A0=A0|=A0=A0Fax +44 207 519 4609=A0=A0=A0|=A0=A0=
Mobile +44 7771 831 052=A0=A0=A0|=A0=A0IP 709513
arun.arumuganainar@tatacommunications.com

-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of rtgwg-request@ietf=
.org
Sent: 01 October 2014 20:01
To: rtgwg@ietf.org
Subject: rtgwg Digest, Vol 118, Issue 2

Send rtgwg mailing list submissions to
	rtgwg@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/rtgwg
or, via email, send a message with subject or body 'help' to
	rtgwg-request@ietf.org

You can reach the person managing the list at
	rtgwg-owner@ietf.org

When replying, please edit your Subject line so it is more specific than "R=
e: Contents of rtgwg digest..."


Today's Topics:

   1. Requesting Comments about the Draft :
      draft-arumuganainar-rtgwg-dps-requirements-00.txt (Bhuvanesh Rajput)
   2. Re: Barry Leiba's No Objection on charter-ietf-rtgwg-04-02:
      (with COMMENT) (Alia Atlas)


----------------------------------------------------------------------

Message: 1
Date: Wed, 1 Oct 2014 15:09:00 +0000
From: Bhuvanesh Rajput <Bhuvanesh.Rajput@tatacommunications.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Requesting Comments about the Draft :
	draft-arumuganainar-rtgwg-dps-requirements-00.txt
Message-ID:
	<E3DFEE681C8ABF4A8AC076EFF3DDD6DEDBF1169A@inp44vdag02.vsnl.co.in>
Content-Type: text/plain; charset=3D"us-ascii"

Hi,

Dynamic path selections draft is well written to have application based fle=
xibility in the routing.

Seek clarification on following


-          Application based traffic offload/routing requirement most often=
 comes from enterprise segment, never seen from service providers.
Since BGP is proposed in the draft to achieve application based routing but=
 BGP is most often used between Autonomous systems (between Service provide=
rs and Enterprise and Service Providers), Why widely accepted and deployed =
IGPs (OSPF and EIGRP) cannot work to achieve proposed functionality? If IGP=
s are supported to have application based routing it will great value add f=
or large Enterprises segment without any major change in existing routing.


-          Draft proposes static configuration to define application profil=
e, how to achieve the routing for the applications dynamic in nature and us=
e dynamic port numbers etc. ?


Regards
Bhuvanesh Rajput

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ietf.org/mail-archive/web/rtgwg/attachments/20141001/94dc8=
d35/attachment.html>

------------------------------

Message: 2
Date: Wed, 1 Oct 2014 11:13:34 -0400
From: Alia Atlas <akatlas@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org"
	<rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>,
	"rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: Re: Barry Leiba's No Objection on charter-ietf-rtgwg-04-02:
	(with COMMENT)
Message-ID:
	<CAG4d1rfyR1WrUGCyiJxT25Mf4+6ZjtdKNj=3D67+m887hPw8A6NA@mail.gmail.com>
Content-Type: text/plain; charset=3D"utf-8"

On Wed, Oct 1, 2014 at 9:34 AM, Barry Leiba <barryleiba@computer.org> wrote=
:

> Barry Leiba has entered the following ballot position for
> charter-ietf-rtgwg-04-02: No Objection
>
> When responding, please keep the subject line intact and reply to all=20
> email addresses included in the To and CC lines. (Feel free to cut=20
> this introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I agree with the comment that "optional" should be removed from the=20
> first sentence.
>

Sure.  It was put in to make it clear that RTGWG isn't a mandatory hurdle f=
or work that is large/organized/ready for a BoF.

Alia


>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ietf.org/mail-archive/web/rtgwg/attachments/20141001/ded44=
3d3/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg


------------------------------

End of rtgwg Digest, Vol 118, Issue 2
*************************************


From nobody Thu Oct  2 07:33:11 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF071A01D0; Thu,  2 Oct 2014 07:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 cu-Fyb7UL2bQ; Thu,  2 Oct 2014 07:33:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 987C21A0008; Thu,  2 Oct 2014 07:33:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Subject: Spencer Dawkins' Yes on charter-ietf-rtgwg-04-03: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141002143306.15658.4375.idtracker@ietfa.amsl.com>
Date: Thu, 02 Oct 2014 07:33:06 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/KFfqiCht9--3yyGws01vSn0Wat0
Cc: rtg-ads@tools.ietf.org, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 14:33:08 -0000

Spencer Dawkins has entered the following ballot position for
charter-ietf-rtgwg-04-03: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-rtgwg/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

As a survivor of a few proposals being Dispatched in RAI, I'm glad to see
RTG adopting a similar model for proposal evaluation.



From nobody Thu Oct  2 07:43:54 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C8C1A037D; Thu,  2 Oct 2014 07:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Ew9QtewDMSrm; Thu,  2 Oct 2014 07:43:51 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD4BB1A03A2; Thu,  2 Oct 2014 07:43:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1315; q=dns/txt; s=iport; t=1412261031; x=1413470631; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=dqAyLmx/DDTtisjpqax7XGvVbI+FKoLnt6Y7TJIUVa4=; b=WsZIfEGkryl0UDvye+sBv3F8xrmvfn92RXG0bMyJKP6CUD27ld58bZp4 OoRO9qaWInq6oa/F9vNGi/edk/bx7Kimj1D234L8pUwDjLkokqkAW8Efe ZMyCbUr71YFmTsb/MDgoJJjBFM61xBihhTvGU+C0jRUns/9kNUQYOX4Pn s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar8EAHtkLVStJssW/2dsb2JhbABgg2FagwHHY4dNAoEhAXuEAwEBAQMBIxVAAQULCxgCAgUWCwICCQMCAQIBRQYBDAEHAQGIMggNpyuWBwEXgSyOGBEBUAeCeIFTAQSGKo9/hwqBZYVzhG2JLoNlO4E+gTsBAQE
X-IronPort-AV: E=Sophos;i="5.04,638,1406592000"; d="scan'208";a="197245249"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 02 Oct 2014 14:43:39 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s92EhcJv028969; Thu, 2 Oct 2014 14:43:39 GMT
Message-ID: <542D649A.1010008@cisco.com>
Date: Thu, 02 Oct 2014 16:43:38 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>, The IESG <iesg@ietf.org>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
References: <20140930192026.30652.78430.idtracker@ietfa.amsl.com>
In-Reply-To: <20140930192026.30652.78430.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/gM7-qhEEcS9Xq05ZcmqJPnAVwjY
Cc: rtgwg@ietf.org, rtgwg-chairs@tools.ietf.org, rtg-ads@tools.ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 14:43:52 -0000

On 30/09/2014 21:20, Adrian Farrel wrote:
> Adrian Farrel has entered the following ballot position for
> charter-ietf-rtgwg-04-02: Yes
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Fully support this: a good change.
>
> I do not believe this change needs to go for external review.
>
> Nit...
> s/an optional venue/a venue/
> (There is nothing in "a venue" that implies compulsion)
>
> ---
>
> Just noticed something we should add:
> RTGWG would be a really good home for routing-related YANG models that
> are not specifically covered by other RTG working groups,
The sentence above is a good addition.
> and for generic
> routing YANG models.
But how is this different than "routing-related YANG models"?
I believe having those two categories adds to the confusion.

Regards, Benoit

> Could this be added as a work item?
>
>
> .
>


From nobody Thu Oct  2 07:53:56 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 818B21A03FF; Thu,  2 Oct 2014 07:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 WDATH497C1Bz; Thu,  2 Oct 2014 07:53:54 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 796321A03E1; Thu,  2 Oct 2014 07:53:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
Subject: Benoit Claise's Block on charter-ietf-rtgwg-04-03: (with BLOCK and COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141002145353.27316.83395.idtracker@ietfa.amsl.com>
Date: Thu, 02 Oct 2014 07:53:53 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/xB7AlmWlwTTkglZ32pJDIIlESa8
Cc: rtg-ads@tools.ietf.org, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 14:53:55 -0000

Benoit Claise has entered the following ballot position for
charter-ietf-rtgwg-04-03: Block

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-rtgwg/



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

Since Adrian's proposal actually made it to the latest proposed charter,
let me file a BLOCK.
> Just noticed something we should add:
> RTGWG would be a really good home for routing-related YANG models that
> are not specifically covered by other RTG working groups,
The sentence above is a good addition.
> and for generic
> routing YANG models.
But how is this different than "routing-related YANG models"?
I believe having those two categories adds to the confusion. Maybe
because I don't understand the difference.

Once this clarification is done, I support RTGWG. It's actually similar
to OPSAWG.


Regards, Benoit


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Editorial point/

RTGWG may also work on specific small topics that do not fit with an
existing
working group. An example of a small topic is a draft that might
otherwise be
AD-sponsored but which could benefit from the review and consensus that
RTGWG
can provide.

Not sure "small" is the right adjective.
In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP
documents, multiple EMAN documents that triggered the EMAN WG creation,
IEEE/IETF MIB relationship RFC). I would remove "small", which equates to
"non important"



From nobody Thu Oct  2 07:57:56 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A03781A03E1; Thu,  2 Oct 2014 07:57:51 -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, SPF_PASS=-0.001] autolearn=ham
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 J6Jq-niyhOlG; Thu,  2 Oct 2014 07:57:49 -0700 (PDT)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1411A01F6; Thu,  2 Oct 2014 07:57:49 -0700 (PDT)
Received: by mail-yk0-f179.google.com with SMTP id 131so1286009ykp.10 for <multiple recipients>; Thu, 02 Oct 2014 07:57:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/oUTnAj6pCJAZtmo+R9+2XQZgNhMyhQJtQGjbeqdt9c=; b=eBrSx2aLJpgTHHsRWDHFsGGzuAlFnikkyj+eh46vTz3IBz2Xt8hhnhM8Vl/l+jWRHW FiGLApV4k6Mt/tOlooIqSCrlQKz6I+6aTp1fKE6tJBbuD43BOpZCdbVxr4Kxfj8ex9sJ aB7LMt3oyYxw+7Pjlv9MI9nGLw8WDEU2lRhl9Sw2hT+D0odrTtRtsl8pgUKo/S9Y+Dho JqEGd7jYhshShEAboYQy3cfkWzJ+GNbEbvvhJlDSZDvtVXW3k14agIyhYB10k4rOXog7 MxhpFaIE0+nVt56WlECu4VWLODobQW01vzmwuLzxVX+NMU8p+SYPkxVkRFDEDTiS0S+s PaRw==
MIME-Version: 1.0
X-Received: by 10.236.41.100 with SMTP id g64mr5623845yhb.60.1412261868946; Thu, 02 Oct 2014 07:57:48 -0700 (PDT)
Received: by 10.170.113.134 with HTTP; Thu, 2 Oct 2014 07:57:48 -0700 (PDT)
In-Reply-To: <542D649A.1010008@cisco.com>
References: <20140930192026.30652.78430.idtracker@ietfa.amsl.com> <542D649A.1010008@cisco.com>
Date: Thu, 2 Oct 2014 10:57:48 -0400
Message-ID: <CAG4d1rdVdStJSYrJ4hbuE_YWcsbjUY=uOEn=q0HM29soz=Eq_A@mail.gmail.com>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=089e0160b3d2074ce8050471d7c0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/iOkkpDaP0DGtN1ZhrpsSBJOVeQg
Cc: Adrian Farrel <adrian@olddog.co.uk>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 14:57:51 -0000

--089e0160b3d2074ce8050471d7c0
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 2, 2014 at 10:43 AM, Benoit Claise <bclaise@cisco.com> wrote:

> On 30/09/2014 21:20, Adrian Farrel wrote:
>
>> Adrian Farrel has entered the following ballot position for
>> charter-ietf-rtgwg-04-02: Yes
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Fully support this: a good change.
>>
>> I do not believe this change needs to go for external review.
>>
>> Nit...
>> s/an optional venue/a venue/
>> (There is nothing in "a venue" that implies compulsion)
>>
>> ---
>>
>> Just noticed something we should add:
>> RTGWG would be a really good home for routing-related YANG models that
>> are not specifically covered by other RTG working groups,
>>
> The sentence above is a good addition.
>
>> and for generic
>> routing YANG models.
>>
> But how is this different than "routing-related YANG models"?
> I believe having those two categories adds to the confusion.
>

routing-related YANG models would be for a particular protocol or routing
service,
while generic routing YANG models may be for specific aspects that aren't
tied to protocol pieces.
At least, that's how I was reading it.  Perhaps Adrian, who suggested the
wording, has some
different feedback.

Alia


> Regards, Benoit
>
>  Could this be added as a work item?
>>
>>
>> .
>>
>>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Oct 2, 2014 at 10:43 AM, Benoit Claise <span dir=3D"ltr">&lt;<a href=3D=
"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div clas=
s=3D"h5">On 30/09/2014 21:20, Adrian Farrel wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Adrian Farrel has entered the following ballot position for<br>
charter-ietf-rtgwg-04-02: Yes<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/<u></u>doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
COMMENT:<br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
<br>
Fully support this: a good change.<br>
<br>
I do not believe this change needs to go for external review.<br>
<br>
Nit...<br>
s/an optional venue/a venue/<br>
(There is nothing in &quot;a venue&quot; that implies compulsion)<br>
<br>
---<br>
<br>
Just noticed something we should add:<br>
RTGWG would be a really good home for routing-related YANG models that<br>
are not specifically covered by other RTG working groups,<br>
</blockquote></div></div>
The sentence above is a good addition.<span class=3D""><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
and for generic<br>
routing YANG models.<br>
</blockquote></span>
But how is this different than &quot;routing-related YANG models&quot;?<br>
I believe having those two categories adds to the confusion.<br></blockquot=
e><div><br></div><div>routing-related YANG models would be for a particular=
 protocol or routing service,</div><div>while generic routing YANG models m=
ay be for specific aspects that aren&#39;t tied to protocol pieces.</div><d=
iv>At least, that&#39;s how I was reading it.=C2=A0 Perhaps Adrian, who sug=
gested the wording, has some</div><div>different feedback.</div><div><br></=
div><div>Alia</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards, Benoit<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><span class=3D"">
Could this be added as a work item?<br>
<br>
<br></span>
.<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div></div>

--089e0160b3d2074ce8050471d7c0--


From nobody Thu Oct  2 08:00:23 2014
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54AF61A1A0A; Thu,  2 Oct 2014 08:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 rB6cqSDplHq3; Thu,  2 Oct 2014 08:00:15 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA75D1A0052; Thu,  2 Oct 2014 08:00:14 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-9f-542d0f757909
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 88.67.25146.57F0D245; Thu,  2 Oct 2014 10:40:22 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Thu, 2 Oct 2014 11:00:12 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
Thread-Topic: Adrian Farrel's Yes on charter-ietf-rtgwg-04-02: (with COMMENT)
Thread-Index: AQHP3OOhpUaOyWPjZkqQA/H3WvYlDJwdJ8cA///Bkwg=
Date: Thu, 2 Oct 2014 15:00:12 +0000
Message-ID: <2CD9B9DB-B321-4449-8303-7020CC5CCEBA@ericsson.com>
References: <20140930192026.30652.78430.idtracker@ietfa.amsl.com>, <542D649A.1010008@cisco.com>
In-Reply-To: <542D649A.1010008@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPgm4Zv26Iwb/3jBY/em4wWxx9LGEx 489EZovnc2ayWNw8OJPJ4sKb38wObB5Tfm9k9Viy5CeTx4rNKxk9vlz+zBbAEsVlk5Kak1mW WqRvl8CVcXNHZsET3or1Py4yNzCu5+5i5OSQEDCR+Lj1JiuELSZx4d56ti5GLg4hgaOMEhvv LYByljFK/Nq4lg2kik3AQOL/t+MsILaIgKpE/9YtLCBFzAK3GCXuvpwFlhAW8JH4vvEtG0SR r8Sl7jlQtpVEw8PXzF2MHBwsAioSu2ZUgpi8AvYSrbPDQCqEBOIk/l9eDVbBKaAp0dQQCRJm BLrt+6k1TCA2s4C4xK0n85kgbhaQWLLnPDOELSrx8vE/VogaHYkFuz+xQdjaEssWvgar4RUQ lDg58wnLBEbRWUhGzULSMgtJyywkLQsYWVYxcpQWp5blphsZbmIExtAxCTbHHYwLPlkeYhTg YFTi4VVw1AkRYk0sK67MPcQozcGiJM6rWT0vWEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAPj Crc66W69fs3ewhuPlP7kzWiv2LkhQmbnLxE2sX+vXaombRRO1RFsjIuSVVZa91tMPmDr7daO yoyz3RGy23yV+xrSzuVv+xug67RR/IHxjAdhuwLv7vEQmhwS76O7L6zh0eeg15VvAyRsmw1f qSZO3f/+qGdmKQOThoJfL2OL86I/hjPCZyuxFGckGmoxFxUnAgASBgAsggIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/eaWIrSntdP2kOv7SrzQi4ybzUTw
Cc: Adrian Farrel <adrian@olddog.co.uk>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 15:00:19 -0000

Agree, I think having in the text "routing-related" only would suffice whil=
e preventing possible confusion.

Regards,
Jeff

> On Oct 2, 2014, at 6:43 PM, Benoit Claise <bclaise@cisco.com> wrote:
>=20
>> On 30/09/2014 21:20, Adrian Farrel wrote:
>> Adrian Farrel has entered the following ballot position for
>> charter-ietf-rtgwg-04-02: Yes
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>=20
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>=20
>> Fully support this: a good change.
>>=20
>> I do not believe this change needs to go for external review.
>>=20
>> Nit...
>> s/an optional venue/a venue/
>> (There is nothing in "a venue" that implies compulsion)
>>=20
>> ---
>>=20
>> Just noticed something we should add:
>> RTGWG would be a really good home for routing-related YANG models that
>> are not specifically covered by other RTG working groups,
> The sentence above is a good addition.
>> and for generic
>> routing YANG models.
> But how is this different than "routing-related YANG models"?
> I believe having those two categories adds to the confusion.
>=20
> Regards, Benoit
>=20
>> Could this be added as a work item?
>>=20
>>=20
>> .
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct  2 08:54:21 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730491A03A0; Thu,  2 Oct 2014 08:54:13 -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, SPF_PASS=-0.001] autolearn=ham
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 uC_6qpbgt5zB; Thu,  2 Oct 2014 08:54:11 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA62E1A0068; Thu,  2 Oct 2014 08:54:10 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id 142so1041115ykq.11 for <multiple recipients>; Thu, 02 Oct 2014 08:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HZjAfx/sIj1VA+5f4RwP9/ykHdCbtUOpPgBLGlebDK4=; b=B3PWWCrl4ZQpXZQT5DIJqKv9zDoBIUsW1/Rq2XbG8E23Z8bx8Hj06K03JmZuPxkJq7 BPDEnwdIRp25g8rb3KJM6B33F00ukoGtO+ZGzJIL1uaRXfx0AmowC+nwkd5gCshWxSOX KEPtz9IS2k/3OolzyQAK/Nty1xxTGJ5n8Qj+Uyo+O1JnkMXNVXNxyX4kXJQE9bunzg7S LlzdvlLBz8jXzw5hzFmU0bx79+kgWv0AQyiaYS88TaQodYIqf8OPudKXx/XhQwzDw09P nA4P4SHuMa9NE/615V/qLNGw5djlNaZS8IYv2qgD1W2UY2SWx26C3bEEYTjE9aKhm3zm nKSg==
MIME-Version: 1.0
X-Received: by 10.236.97.38 with SMTP id s26mr5847717yhf.107.1412265249926; Thu, 02 Oct 2014 08:54:09 -0700 (PDT)
Received: by 10.170.113.134 with HTTP; Thu, 2 Oct 2014 08:54:09 -0700 (PDT)
In-Reply-To: <20141002145353.27316.83395.idtracker@ietfa.amsl.com>
References: <20141002145353.27316.83395.idtracker@ietfa.amsl.com>
Date: Thu, 2 Oct 2014 11:54:09 -0400
Message-ID: <CAG4d1re99399FdXCim8ZjZd1JQh857qe+OWpNj9+BDZk9Be74A@mail.gmail.com>
Subject: Re: Benoit Claise's Block on charter-ietf-rtgwg-04-03: (with BLOCK and COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c1ca848cf2f8050472a08a
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/gnE2GlxirDH3kZryCFAb-2w2fD8
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 15:54:13 -0000

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

On Thu, Oct 2, 2014 at 10:53 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Benoit Claise has entered the following ballot position for
> charter-ietf-rtgwg-04-03: Block
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>
>
>
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
>
> Since Adrian's proposal actually made it to the latest proposed charter,
> let me file a BLOCK.
> > Just noticed something we should add:
> > RTGWG would be a really good home for routing-related YANG models that
> > are not specifically covered by other RTG working groups,
> The sentence above is a good addition.
> > and for generic
> > routing YANG models.
> But how is this different than "routing-related YANG models"?
> I believe having those two categories adds to the confusion. Maybe
> because I don't understand the difference.
>
> Once this clarification is done, I support RTGWG. It's actually similar
> to OPSAWG.
>

As I sent in another email, I can see some differences - but don't feel
strongly that
it adds anything.  I've updated the charter to remove the "generic routing
YANG models"
versus the routing-related ones.

Alia


> Regards, Benoit
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Editorial point/
>
> RTGWG may also work on specific small topics that do not fit with an
> existing
> working group. An example of a small topic is a draft that might
> otherwise be
> AD-sponsored but which could benefit from the review and consensus that
> RTGWG
> can provide.
>
> Not sure "small" is the right adjective.
> In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP
> documents, multiple EMAN documents that triggered the EMAN WG creation,
> IEEE/IETF MIB relationship RFC). I would remove "small", which equates to
> "non important"
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Oct 2, 2014 at 10:53 AM, Benoit Claise <span dir=3D"ltr">&lt;<a href=3D=
"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Benoit Claise has entered the f=
ollowing ballot position for<br>
charter-ietf-rtgwg-04-03: Block<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
BLOCK:<br>
----------------------------------------------------------------------<br>
<br>
Since Adrian&#39;s proposal actually made it to the latest proposed charter=
,<br>
let me file a BLOCK.<br>
&gt; Just noticed something we should add:<br>
&gt; RTGWG would be a really good home for routing-related YANG models that=
<br>
&gt; are not specifically covered by other RTG working groups,<br>
The sentence above is a good addition.<br>
&gt; and for generic<br>
&gt; routing YANG models.<br>
But how is this different than &quot;routing-related YANG models&quot;?<br>
I believe having those two categories adds to the confusion. Maybe<br>
because I don&#39;t understand the difference.<br>
<br>
Once this clarification is done, I support RTGWG. It&#39;s actually similar=
<br>
to OPSAWG.<br></blockquote><div><br></div><div>As I sent in another email, =
I can see some differences - but don&#39;t feel strongly that</div><div>it =
adds anything.=C2=A0 I&#39;ve updated the charter to remove the &quot;gener=
ic routing YANG models&quot;</div><div>versus the routing-related ones.</di=
v><div><br></div><div>Alia</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
Regards, Benoit<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Editorial point/<br>
<br>
RTGWG may also work on specific small topics that do not fit with an<br>
existing<br>
working group. An example of a small topic is a draft that might<br>
otherwise be<br>
AD-sponsored but which could benefit from the review and consensus that<br>
RTGWG<br>
can provide.<br>
<br>
Not sure &quot;small&quot; is the right adjective.<br>
In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP<br=
>
documents, multiple EMAN documents that triggered the EMAN WG creation,<br>
IEEE/IETF MIB relationship RFC). I would remove &quot;small&quot;, which eq=
uates to<br>
&quot;non important&quot;<br>
<br>
<br>
</blockquote></div><br></div></div>

--001a11c1ca848cf2f8050472a08a--


From nobody Thu Oct  2 09:04:27 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA541A1A36; Thu,  2 Oct 2014 09:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 UAshhjlxSbS7; Thu,  2 Oct 2014 09:04:24 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F0E1A1A92; Thu,  2 Oct 2014 09:04:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
Subject: Benoit Claise's No Objection on charter-ietf-rtgwg-04-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141002160424.23161.56016.idtracker@ietfa.amsl.com>
Date: Thu, 02 Oct 2014 09:04:24 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/kqUbYkhfb09pmq66B9U-_RTzhD4
Cc: rtg-ads@tools.ietf.org, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 16:04:25 -0000

Benoit Claise has entered the following ballot position for
charter-ietf-rtgwg-04-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-rtgwg/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Editorial point/

RTGWG may also work on specific small topics that do not fit with an
existing
working group. An example of a small topic is a draft that might
otherwise be
AD-sponsored but which could benefit from the review and consensus that
RTGWG
can provide.

Not sure "small" is the right adjective.
In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP
documents, multiple EMAN documents that triggered the EMAN WG creation,
IEEE/IETF MIB relationship RFC). I would remove "small", which equates to
"non important"



From nobody Thu Oct  2 09:07:36 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 337E71A1A36; Thu,  2 Oct 2014 09:07:34 -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, SPF_PASS=-0.001] autolearn=ham
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 UPc9JfCTTtYj; Thu,  2 Oct 2014 09:07:29 -0700 (PDT)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 279B91A8773; Thu,  2 Oct 2014 09:07:23 -0700 (PDT)
Received: by mail-yk0-f173.google.com with SMTP id 200so1331657ykr.18 for <multiple recipients>; Thu, 02 Oct 2014 09:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fG2JENnPnUhNuKzPJ5m2prGMODjc/HO7uLgtx6zTpRU=; b=AMtMongrpz0qv7C93AGocAL/jxSWYStWWN8lHc0gTA9C93kUkNYMxc4W0P7l0pztup YsqUROJc6hsDr4glnWjgQXuEXZ0MFtmO+JrayP72Tf7vVhc8hMWqKHrPfGWlw1YZlyp2 Rq8hZ8MzZh8LeCWEP2Eu3kJvNfYZl/FkUzlIPc6E7RBr72t8FqXU0JM/FCVJpK2fglH7 mBvq1YtHIpLb3YbNfUbSuf/CxSWdBFavUfTg6NuEis7qKbAbtREJmLfjWdagz8CMIRqU w62WywjKiPMTeU8Q2dAN0Vs3/KDRpXYj/6euZK1GNoIGZjH0M/rkq/eUQyeFzkba9j88 zd0Q==
MIME-Version: 1.0
X-Received: by 10.236.61.100 with SMTP id v64mr5981849yhc.77.1412266042402; Thu, 02 Oct 2014 09:07:22 -0700 (PDT)
Received: by 10.170.113.134 with HTTP; Thu, 2 Oct 2014 09:07:22 -0700 (PDT)
In-Reply-To: <20141002160424.23161.56016.idtracker@ietfa.amsl.com>
References: <20141002160424.23161.56016.idtracker@ietfa.amsl.com>
Date: Thu, 2 Oct 2014 12:07:22 -0400
Message-ID: <CAG4d1rdFruSFGEU+8qOvxCb6rV2Q32vStefOduMvaeDh5N683A@mail.gmail.com>
Subject: Re: Benoit Claise's No Objection on charter-ietf-rtgwg-04-04: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=089e0158be1cc92c17050472cff1
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/a8FD2_X_SH18Lou56S0xQPhe5jE
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 16:07:34 -0000

--089e0158be1cc92c17050472cff1
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 2, 2014 at 12:04 PM, Benoit Claise <bclaise@cisco.com> wrote:

> Benoit Claise has entered the following ballot position for
> charter-ietf-rtgwg-04-04: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-rtgwg/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Editorial point/
>
> RTGWG may also work on specific small topics that do not fit with an
> existing
> working group. An example of a small topic is a draft that might
> otherwise be
> AD-sponsored but which could benefit from the review and consensus that
> RTGWG
> can provide.
>
> Not sure "small" is the right adjective.
> In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP
> documents, multiple EMAN documents that triggered the EMAN WG creation,
> IEEE/IETF MIB relationship RFC). I would remove "small", which equates to
> "non important"
>

If a topic transitions from small to big, then a recharter is needed to
include it.
I disagree that small equates to non-important.  I don't have a better word
than small
- particularly teamed with the example.


>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Oct 2, 2014 at 12:04 PM, Benoit Claise <span dir=3D"ltr">&lt;<a href=3D=
"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Benoit Claise has entered the f=
ollowing ballot position for<br>
charter-ietf-rtgwg-04-04: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/charter-ietf-rtgwg/" target=3D"_=
blank">http://datatracker.ietf.org/doc/charter-ietf-rtgwg/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Editorial point/<br>
<br>
RTGWG may also work on specific small topics that do not fit with an<br>
existing<br>
working group. An example of a small topic is a draft that might<br>
otherwise be<br>
AD-sponsored but which could benefit from the review and consensus that<br>
RTGWG<br>
can provide.<br>
<br>
Not sure &quot;small&quot; is the right adjective.<br>
In OPSAWG, we had small topics that became big topics (example: 3 CAPWAP<br=
>
documents, multiple EMAN documents that triggered the EMAN WG creation,<br>
IEEE/IETF MIB relationship RFC). I would remove &quot;small&quot;, which eq=
uates to<br>
&quot;non important&quot;<br></blockquote><div><br></div><div>If a topic tr=
ansitions from small to big, then a recharter is needed to include it.</div=
><div>I disagree that small equates to non-important.=C2=A0 I don&#39;t hav=
e a better word than small=C2=A0</div><div>- particularly teamed with the e=
xample.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
_______________________________________________<br>
rtgwg mailing list<br>
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/rtgwg</a><br>
</blockquote></div><br></div></div>

--089e0158be1cc92c17050472cff1--


From nobody Fri Oct  3 16:39:31 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2AC71A1A02; Fri,  3 Oct 2014 16:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 BTWBW1olXvtg; Fri,  3 Oct 2014 16:39:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDB31A8849; Fri,  3 Oct 2014 16:39:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Rechartered Routing Area Working Group (rtgwg)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141003233926.32433.32317.idtracker@ietfa.amsl.com>
Date: Fri, 03 Oct 2014 16:39:26 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/tdg_9a47vkfjrPgKIu4x5ZIwXuo
Cc: rtgwg WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Oct 2014 23:39:29 -0000

The Routing Area Working Group (rtgwg) working group in the Routing Area
of the IETF has been rechartered. For additional information please
contact the Area Directors or the WG Chairs.

Routing Area Working Group (rtgwg)
------------------------------------------------
Current Status: Active WG

Chairs:
  Jeff Tantsura <jeff.tantsura@ericsson.com>
  Alvaro Retana <aretana@cisco.com>

Assigned Area Director:
  Alia Atlas <akatlas@gmail.com>

Mailing list
  Address: rtgwg@ietf.org
  To Subscribe: rtgwg-request@ietf.org
  Archive: http://www.ietf.org/mail-archive/web/rtgwg/

Charter:

The Routing Area working group (RTGWG) is chartered to provide a
venue to discuss, evaluate, support and develop proposals for 
new work in the Routing Area and may work on specific small topics
that do not fit with an existing working group. 

Options for handling new work include:

- Directing the work to an existing WG (including RTGWG)
- Developing a proposal for a BoF.
- Developing a charter and establishing consensus for a new WG.  This
option will primarily be used with fairly mature and/or well-defined
efforts.
- Careful evaluation, leading to deferring or rejecting work.

It is expected that the proposals for new work will only include items
which
are not aligned with the work of other WGs or that may span multiple WGs.
The Area Directors and WG Chairs can provide guidance if there is any
doubt whether a topic should be discussed in RTGWG.

A major objective of the RTGWG is to provide timely, clear
dispositions of new efforts. Where there is consensus to take
on new work, the WG will strive to quickly find a home for it.
Reconsideration of proposals which have failed to gather consensus
will be prioritized behind proposals for new work which have not
yet been considered. In general, requests for reconsideration
should only be made once a proposal has been significantly
revised.

If RTGWG decides that a particular topic should be addressed by
a new WG, the chairs will recommend the work to the Routing ADs
with a summary of the evaluation.  The Routing ADs may then choose
to follow the normal IETF chartering process (potential BoF, IETF-wide
review of the proposed charter, etc.).

Guiding principles for evaluation of new work by RTGWG will include:

   1. Providing a clear problem statement for proposed new work.

   2. Prioritizing new efforts to manage the trade-offs between urgency,
       interest, and available resources in the Routing Area.

   3. Looking for commonalities among ongoing efforts.
       Such commonalities may indicate the need to develop more
       general, reusable solutions.  

   4. Ensuring appropriate cross-WG and cross-area review.

   5. Protecting the architectural integrity of the protocols developed
       in the Routing Area and ensuring that work has significant
applicability.

RTGWG may also work on specific small topics that do not fit with an
existing working group. An example of a small topic is a draft that might
otherwise be AD-sponsored but which could benefit from the review and
consensus that RTGWG can provide.  

RTGWG may work on larger topics, but must be explicitly rechartered to
add the topic.  The specific larger topics that RTGWG is currently
chartered to work on:

  * Enhancements to hop-by-hop distributed
    routing (e.g., multicast, LDP-MPLS, unicast routing) related to
    fast-reroute and loop-free convergence. A specific goal of
    fast-reroute mechanisms is to provide up to complete coverage when
    the potential failure would not partition the network. All work in
    this area should be specifically evaluated by the WG in terms of
    practicality and applicability to deployed networks.

  * Routing-related YANG models that are not appropriate for other RTG
working
    groups. 

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. 

Milestones:
  Nov 2012 - Submit Composite-Link Requirements to IESG for publication
as Informational
  Nov 2012 - Submit initial Internet Draft on Multicast IP Fast Reroute
Architecture
  Nov 2012 - Submit Composite-Link Framework to IESG for publication as
Informational
  Apr 2013 - Submit specification on Advanced IP Fast Reroute mechanism
to IESG for publication as Proposed Standard



From nobody Mon Oct  6 15:19:36 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484851A8AB6; Mon,  6 Oct 2014 15:19:31 -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, SPF_PASS=-0.001] autolearn=ham
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 zRXaCB5fpe6S; Mon,  6 Oct 2014 15:19:29 -0700 (PDT)
Received: from mail-yk0-x236.google.com (mail-yk0-x236.google.com [IPv6:2607:f8b0:4002:c07::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42A4C1A8913; Mon,  6 Oct 2014 15:19:29 -0700 (PDT)
Received: by mail-yk0-f182.google.com with SMTP id 131so2347320ykp.41 for <multiple recipients>; Mon, 06 Oct 2014 15:19:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=1fPiCtUO5Bu1eDzi8oncCocfnYFwXKjBjZT9JwNBsg4=; b=EKIEMRO2azqh11/TpJWPpvXOG5A4WuqaYpU0gbowzuWeFQgeP5zyMBXLm4gqFz0nQZ +RjMxzurQWnjHS0lnpcZN82lg24wPK2JNIcyO3SJMpedM4ZpCPDi7lJwipXUTbm44iMT NZVYSzArFnDr5elTVWsOTZZO+ZgT/0N4iDgQI74p3uIQ3qrH7IBRz+HDzUJFQeQTEt2o DtHFkY5WGkDjhnUPcFoZBHfaH+pJw8boNOhzCcvZf+H8KBX+/OBVURqeyjPyEST73mXb UIUSuP0u1iK47OI4/YjL2eWCXS61/zMw6iHMMMKP+JaJ5QrbZpZ78BB7byozWm/9jCo1 aKCw==
MIME-Version: 1.0
X-Received: by 10.236.87.227 with SMTP id y63mr28746561yhe.25.1412633968630; Mon, 06 Oct 2014 15:19:28 -0700 (PDT)
Received: by 10.170.113.134 with HTTP; Mon, 6 Oct 2014 15:19:28 -0700 (PDT)
Date: Mon, 6 Oct 2014 18:19:28 -0400
Message-ID: <CAG4d1rda3r3iVXyQ_GD7tC9-BWctq0o8o5WrfiVciELNYMZJbg@mail.gmail.com>
Subject: Creation of rtg-yang-coord mailing list
From: Alia Atlas <akatlas@gmail.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>,  "isis-wg@ietf.org" <isis-wg@ietf.org>, OSPF List <ospf@ietf.org>, "idr@ietf. org" <idr@ietf.org>,  "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3010eabde5e0fb0504c879ae
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Nl39VEGmiMUsmdt5OQt4QQdImfE
Cc: Benoit Claise <bclaise@cisco.com>, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 06 Oct 2014 22:19:31 -0000

--20cf3010eabde5e0fb0504c879ae
Content-Type: text/plain; charset=UTF-8

The rtg-yang-coord mailing list will provide a forum for coordination of
the development  of YANG models being worked on for Routing, in order to
provide a consistent view to the NMS.  The intended participants are people
active in Routing working groups and interested in the associated YANG
models, and YANG experts assisting with Routing YANG models. While this
list will help with the synchronization, WGs with responsibility for
core routing protocols are expected  to also be responsible for the
development of YANG models for those  protocols.

To subscribe, visit:

https://www.ietf.org/mailman/listinfo/rtg-yang-coord

Regards,

Alia

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

<div dir=3D"ltr"><p style=3D"color:rgb(0,0,0);font-family:&#39;Times New Ro=
man&#39;;font-size:medium">The rtg-yang-coord mailing list will provide a f=
orum for coordination of the development=C2=A0=C2=A0of YANG models being wo=
rked on for Routing, in order to provide a=C2=A0consistent view to the NMS.=
=C2=A0 The intended participants are people active in Routing working group=
s and interested in the=C2=A0associated YANG models, and YANG experts assis=
ting with Routing YANG=C2=A0models. While this list=C2=A0will help with the=
 synchronization, WGs with responsibility for core=C2=A0routing protocols a=
re expected=C2=A0=C2=A0to also be responsible for the development of YANG m=
odels for those=C2=A0=C2=A0protocols.=C2=A0</p><p style=3D"color:rgb(0,0,0)=
;font-family:&#39;Times New Roman&#39;;font-size:medium">To subscribe, visi=
t:</p><p style><font color=3D"#000000" face=3D"Times New Roman" size=3D"3">=
<a href=3D"https://www.ietf.org/mailman/listinfo/rtg-yang-coord">https://ww=
w.ietf.org/mailman/listinfo/rtg-yang-coord</a></font><br></p><p style>Regar=
ds,</p><p style>Alia</p></div>

--20cf3010eabde5e0fb0504c879ae--


From nobody Sat Oct 11 04:28:22 2014
Return-Path: <aretana@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBDA11A035D for <rtgwg@ietfa.amsl.com>; Sat, 11 Oct 2014 04:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level: 
X-Spam-Status: No, score=-15.286 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, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 rRxO1Q02iN74 for <rtgwg@ietfa.amsl.com>; Sat, 11 Oct 2014 04:28:19 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6DE91A0359 for <rtgwg@ietf.org>; Sat, 11 Oct 2014 04:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4478; q=dns/txt; s=iport; t=1413026899; x=1414236499; h=from:to:cc:subject:date:message-id:mime-version; bh=RlGHiTvwzHseMynk2cmZdL8P0OCF9A4sY63AgzXVoEg=; b=hSsE7ZAbgPkzfJuXkJhmXbpbutkqkMk/8P+H7Mtsu4rIP4OCyaHO3/oK IsLTSrxSyfnp3dLWS4Gb4ocz6B5nIfCg43f8ZVoDPp9gzuAn8YZVy+jZz k0KZNG148+s/cnQwRekZl3TjoQgEqwVvMvgyUdfE7cLQN86x2Yj7P5ZAJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYHAJgTOVStJV2Y/2dsb2JhbABggkhGU1gEhWK1Q44rgW2HTYEDFgFyCYQKeRIBDHQnBA6IQw2/RAEBAQEBBQEBAQEBAQEbj2IRAUwEhFIFj1+CGoRChxCBLjyDCpEdgV2CGmwBgQ45gQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,697,1406592000";  d="scan'208,217";a="362495516"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 11 Oct 2014 11:28:18 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9BBSHkG002004 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 11 Oct 2014 11:28:17 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.127]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Sat, 11 Oct 2014 06:28:17 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: IETF 91 Agenda Items (rtgwg)
Thread-Topic: IETF 91 Agenda Items (rtgwg)
Thread-Index: AQHP5UZz9a0iPd7BHUO+9kysIBuzVA==
Date: Sat, 11 Oct 2014 11:28:16 +0000
Message-ID: <D05E8C8D.6D2FB%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.3]
Content-Type: multipart/alternative; boundary="_000_D05E8C8D6D2FBaretanaciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/yhzj_cGxIS_d5asZT6owg-akOR4
Cc: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 11 Oct 2014 11:28:21 -0000

--_000_D05E8C8D6D2FBaretanaciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi!

The preliminary agenda for Honolulu was posted yesterday (https://datatrack=
er.ietf.org/meeting/91/agenda.txt), and rtgwg is scheduled to meet as follo=
ws:

WEDNESDAY, November 12, 2014

0900-1130  Morning Session I
Coral 2                 RTG     rtgwg           Routing Area Working Group =
WG


>From here on the dates look like this:

  *   2014-10-27 (Monday): Internet Draft submission cut-off (for all draft=
s, including -00)
  *   2014-10-27 (Monday): Draft Working Group agendas due
  *   2014-11-03 (Monday): Revised Working Group agendas due

Note that the ID submission cut-off and the Draft WG Agendas are due on the=
 same day.  Please reply to this email with any requests by Friday Oct/24 t=
o be included in the Draft WG Agenda.  Note that the ID MUST have already b=
een published to be considered.

For a draft to be considered for the Final  WG Agenda:

  1.  It MUST have been published already.
  2.  The authors SHOULD start a discussion on the list highlighting the ma=
in points of the draft (don=92t just send a copy of the announcement and/or=
 paste the abstract).
  3.  Slides MUST be provided to the chairs by EOD on Monday Nov/10.

We will prioritize existing WG items first, followed by work explicitly ide=
ntified in the WG charter.  Other items may be considered if we have time; =
we will give preference to items for which there has been a discussion on t=
he list on a first-come basis.  As we recently discussed on the list, the C=
harter was modified:  http://datatracker.ietf.org/wg/rtgwg/charter/   Jeff =
and I are working on updating the milestones.

Thanks!

Alvaro + Jeff

--_000_D05E8C8D6D2FBaretanaciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <D4292741B416864D848E3BD0976200D4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi!</div>
<div><br>
</div>
<div>The preliminary agenda for Honolulu was posted yesterday (<a href=3D"h=
ttps://datatracker.ietf.org/meeting/91/agenda.txt">https://datatracker.ietf=
.org/meeting/91/agenda.txt</a>), and rtgwg is scheduled to meet as follows:=
</div>
<div>
<pre>WEDNESDAY, November 12, 2014

0900-1130  Morning Session I
Coral 2         	RTG 	rtgwg       	Routing Area Working Group WG
</pre>
</div>
<div>From here on the dates look like this:</div>
<div>
<ul>
<li><strong>2014-10-27 (Monday):</strong> Internet Draft submission cut-off=
 (for all drafts, including -00)&nbsp;</li><li><strong>2014-10-27 (Monday):=
</strong> Draft Working Group agendas due&nbsp;</li><li><strong>2014-11-03 =
(Monday):</strong> Revised Working Group agendas due&nbsp;</li></ul>
</div>
<div>Note that the ID submission cut-off and the Draft WG Agendas are due o=
n the same day. &nbsp;Please reply to this email with any requests by Frida=
y Oct/24 to be included in the Draft WG Agenda. &nbsp;Note that the ID MUST=
 have already been published to be considered.</div>
<div><br>
</div>
<div>For a draft to be considered for the Final &nbsp;WG Agenda:</div>
<ol>
<li>It MUST have been published already.</li><li>The authors SHOULD start a=
 discussion on the list highlighting the main points of the draft (don=92t =
just send a copy of the announcement and/or paste the abstract).</li><li>Sl=
ides MUST be provided to the chairs by EOD on Monday Nov/10.</li></ol>
<div>We will prioritize existing WG items first, followed by work explicitl=
y identified in the WG charter. &nbsp;Other items may be considered if we h=
ave time; we will give preference to items for which there has been a discu=
ssion on the list on a first-come basis.
 &nbsp;As we recently discussed on the list, the Charter was modified: &nbs=
p;<a href=3D"http://datatracker.ietf.org/wg/rtgwg/charter">http://datatrack=
er.ietf.org/wg/rtgwg/charter</a>/ &nbsp; Jeff and I are working on updating=
 the milestones.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro &#43; Jeff</div>
</body>
</html>

--_000_D05E8C8D6D2FBaretanaciscocom_--


From nobody Wed Oct 15 10:44:21 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF751A1B7C for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 10:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 ZKYAArywEOnM for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 10:44:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0290D1A8F49 for <rtgwg@ietf.org>; Wed, 15 Oct 2014 10:44:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: rtgwg@ietf.org
Subject: Milestones changed for rtgwg WG
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141015174418.32312.83800.idtracker@ietfa.amsl.com>
Date: Wed, 15 Oct 2014 10:44:18 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/7TEJg9giwnygRzaCLVa_epgxzBY
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2014 17:44:20 -0000

Changed milestone "Submit Composite-Link Requirements to IESG for
publication as Informational", set due date to March 2015 from
November 2012, added draft-ietf-rtgwg-cl-use-cases to milestone.

Changed milestone "Submit initial Internet Draft on Multicast IP Fast
Reroute Architecture", set due date to March 2015 from November 2012,
added draft-ietf-rtgwg-mofrr to milestone.

Changed milestone "Submit Composite-Link Framework to IESG for
publication as Informational", set due date to March 2015 from
November 2012, added draft-ietf-rtgwg-cl-framework to milestone.

Changed milestone "Submit specification on Advanced IP Fast Reroute
mechanism to IESG for publication as Proposed Standard", set due date
to July 2015 from April 2013, added
draft-ietf-rtgwg-mrt-frr-architecture,
draft-ietf-rtgwg-mrt-frr-algorithm to milestone.

URL: http://datatracker.ietf.org/wg/rtgwg/charter/


From nobody Wed Oct 15 10:49:16 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8B71A903A for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 10:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 mK08FcelXqxz for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 10:49:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6351AC40C for <rtgwg@ietf.org>; Wed, 15 Oct 2014 10:49:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: rtgwg@ietf.org
Subject: Milestones changed for rtgwg WG
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141015174911.429.67242.idtracker@ietfa.amsl.com>
Date: Wed, 15 Oct 2014 10:49:11 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/B7pcfdOtd6EPR2l74BxXPv8DbQc
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2014 17:49:14 -0000

Changed milestone "Submit Remote LFA (link protection) for publication
as Proposed Standard", set state to active from review, accepting new
milestone.

Changed milestone "Submit Document on Operational Experience of using
BGP in a Data Center for publication as Informational", set state to
active from review, accepting new milestone.

Changed milestone "Submit Operational Management for LFA for
publication as Proposed Standard", set state to active from review,
accepting new milestone.

Changed milestone "Submit Remote LFA (node protection) for publication
as Proposed Standard", set state to active from review, accepting new
milestone.

Changed milestone "Submit MIB for IP Fast-Reroute for publication as
Proposed Standard", set state to active from review, accepting new
milestone.

URL: http://datatracker.ietf.org/wg/rtgwg/charter/


From nobody Wed Oct 15 16:32:09 2014
Return-Path: <uma.chunduri@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0ED71ACE14 for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 16:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 5ZmRLvLfKRSi for <rtgwg@ietfa.amsl.com>; Wed, 15 Oct 2014 16:31:59 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2852F1ACDDB for <rtgwg@ietf.org>; Wed, 15 Oct 2014 16:31:59 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-63-543eaa37a7b0
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E2.F8.25146.73AAE345; Wed, 15 Oct 2014 19:09:11 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0174.001; Wed, 15 Oct 2014 19:31:57 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-chunduri-rtgwg-lfa-extended-procedures-00.txt
Thread-Topic: New Version Notification for draft-chunduri-rtgwg-lfa-extended-procedures-00.txt
Thread-Index: AQHP6M7TjkGdAdFugUqdNRduVLco45wxzptg
Date: Wed, 15 Oct 2014 23:31:57 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F3C9BB2@eusaamb105.ericsson.se>
References: <20141015232154.12677.54716.idtracker@ietfa.amsl.com>
In-Reply-To: <20141015232154.12677.54716.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyuXRPlK75KrsQg4nHFS0uvPnN7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujP1rm9kKPvFXnLrayt7AuIe/i5GTQ0LAROLnndnsELaYxIV7 69m6GLk4hASOMkrM2nKbGcJZziixbcYPsCo2AT2Jj1N/gtkiAqoSvbNa2UBsYYF4iXW3zzNB xBMktt87xAhhG0nsPrcFrJ4FqH7m76NAcQ4OXgFfiR+HxUHCQgKOEifmP2ABsTkFnCT23D3B DGIzAh30/dQasJHMAuISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YIWwliUlLz7GCjGcW0JRYv0sf olVRYkr3Q7ALeAUEJU7OfMIygVF0FpKpsxA6ZiHpmIWkYwEjyypGjtLi1LLcdCPDTYzAoD8m wea4g3HBJ8tDjAIcjEo8vA/m2IYIsSaWFVfmHmKU5mBREufVrJ4XLCSQnliSmp2aWpBaFF9U mpNafIiRiYNTqoExPljzs8m2hS6HGFZ4Xg1fFfN6D6sZa+SXp0fWz5jpEt0SMXmrvfJr/v1h m59zNJaL7Ko+G1p4u7n5G6NoJI9gybxnXr+2pYaITXBq+Llq/eckw3fX7whH9k6YdtpOT2j6 k5CZFx7b/JjbeNr5wWsjtet1q9YxGR6pZgkw7HMyDP98/NP3yQzrlViKMxINtZiLihMBAYJc WVsCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/cwQICWwWCgz4GbS6wYN2_icYxNY
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2014 23:32:00 -0000

RGVhciBSVEdXRywNCg0KWW91ciBjb21tZW50cyBhbmQgc3VnZ2VzdGlvbnMgd291bGQgYmUgZ3Jl
YXRseSBhcHByZWNpYXRlZC4NCg0KLS0NClVtYSBDLg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmddIA0KU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDE1LCAyMDE0IDQ6MjIg
UE0NClRvOiBVbWEgQ2h1bmR1cmk7IEplZmYgVGFudHN1cmE7IFVtYSBDaHVuZHVyaTsgSmVmZiBU
YW50c3VyYQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1jaHVu
ZHVyaS1ydGd3Zy1sZmEtZXh0ZW5kZWQtcHJvY2VkdXJlcy0wMC50eHQNCg0KDQpBIG5ldyB2ZXJz
aW9uIG9mIEktRCwgZHJhZnQtY2h1bmR1cmktcnRnd2ctbGZhLWV4dGVuZGVkLXByb2NlZHVyZXMt
MDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFVtYSBDaHVuZHVyaSBh
bmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCk5hbWU6CQlkcmFmdC1jaHVuZHVy
aS1ydGd3Zy1sZmEtZXh0ZW5kZWQtcHJvY2VkdXJlcw0KUmV2aXNpb246CTAwDQpUaXRsZToJCUV4
dGVuZGVkIHByb2NlZHVyZXMgYW5kIGNvbnNpZGVyYXRpb25zIGZvciBldmFsdWF0aW5nIExvb3At
RnJlZSBBbHRlcm5hdGVzDQpEb2N1bWVudCBkYXRlOgkyMDE0LTEwLTE1DQpHcm91cDoJCUluZGl2
aWR1YWwgU3VibWlzc2lvbg0KUGFnZXM6CQk4DQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtY2h1bmR1cmktcnRnd2ctbGZhLWV4dGVuZGVk
LXByb2NlZHVyZXMtMDAudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtY2h1bmR1cmktcnRnd2ctbGZhLWV4dGVuZGVkLXByb2NlZHVyZXMv
DQpIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2h1bmR1
cmktcnRnd2ctbGZhLWV4dGVuZGVkLXByb2NlZHVyZXMtMDANCg0KDQpBYnN0cmFjdDoNCiAgIFRo
aXMgZG9jdW1lbnQgcHJvdmlkZSBmZXcgY2xhcmlmaWNhdGlvbnMgYW5kIGV4dGVuZGVkIHByb2Nl
ZHVyZXMgdG8NCiAgIElQIEZhc3QgUmVyb3V0ZSB1c2luZyBMb29wLUZyZWUgQWx0ZXJuYXRlcyBh
cyBkZWZpbmVkIGluIFJGQyA1Mjg2Lg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0K
UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhl
IHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBh
cmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0K
DQo=


From nobody Mon Oct 20 13:40:59 2014
Return-Path: <equinox@diac24.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C1611ACE5C for <rtgwg@ietfa.amsl.com>; Mon, 20 Oct 2014 13:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 i7GRmAqkfsxS for <rtgwg@ietfa.amsl.com>; Mon, 20 Oct 2014 13:40:53 -0700 (PDT)
Received: from spaceboyz.net (spaceboyz.net [IPv6:2001:8d8:870:1000::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D00021ACE57 for <rtgwg@ietf.org>; Mon, 20 Oct 2014 13:40:52 -0700 (PDT)
Received: from [2001:8d8:870:10ef:1::] (helo=jupiter.n2.diac24.net) by spaceboyz.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from <equinox@diac24.net>) id 1XgJl2-0003Fm-BE; Mon, 20 Oct 2014 22:40:48 +0200
Received: from equinox by jupiter.n2.diac24.net with local (Exim 4.82) (envelope-from <equinox@diac24.net>) id 1XgJkn-003PxX-At; Mon, 20 Oct 2014 22:40:36 +0200
Date: Mon, 20 Oct 2014 22:40:33 +0200
From: David Lamparter <equinox@diac24.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141020204033.GD236844@jupiter.n2.diac24.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/uGXZYWFiPGN2CNyBwJlZgImi7s8
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 Oct 2014 20:40:57 -0000

Hi rtgwg,


freshly submitted & soliciting for feedback are the following drafts:
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-qualifiers/?include_text=1
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?include_text=1

These are distilled version of the SADR stuff that has been coming in
from homenet; they describe the hop-by-hop forwarding behaviour
independent of the dynamic routing protocol du jour.  The first one
describes general considerations of adding things ("extra qualifiers")
to destination longest-match, the second one does the specifics for
source match.  They're derived from baker-ipv6-isis-dst-src-routing, and
are essentially write-ups of e-mail threads with Fred.  (Thanks!)

These are -00, so there's a lot of things to be fixed still (I'm not
even sure whether this should be 2 drafts or 1, and some bits should be
moved from -dst-src to -extra-qualifiers if it stays separate.)

I believe rtgwg is the "best" wg for this, looking at the charter this
fits "Enhancements to hop-by-hop distributed routing", though admittedly
it's neither FRR nor LFA.  I'll happily accept a redirect to another wg
(6man? homenet?) if that's deemed more appropriate.

Last but not least, I'd like to request a slot at the IETF 91 rtgwg
meeting to present these drafts.

Cheers & Thanks in advance for feedback,


-David


From nobody Mon Oct 20 19:51:52 2014
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A50E1A1AB4 for <rtgwg@ietfa.amsl.com>; Mon, 20 Oct 2014 19:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.012
X-Spam-Level: 
X-Spam-Status: No, score=-1.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_46=0.6, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKHa5ItAFLdx for <rtgwg@ietfa.amsl.com>; Mon, 20 Oct 2014 19:51:49 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C34A1A1AAA for <rtgwg@ietf.org>; Mon, 20 Oct 2014 19:51:49 -0700 (PDT)
Received: from puck.nether.net (localhost [127.0.0.1]) by puck.nether.net (8.14.8/8.14.5) with ESMTP id s9L2o6Hs003206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Oct 2014 22:50:06 -0400
Received: (from jrmitche@localhost) by puck.nether.net (8.14.8/8.14.8/Submit) id s9L2o67u003203; Mon, 20 Oct 2014 22:50:06 -0400
Date: Mon, 20 Oct 2014 22:50:05 -0400
From: Jon Mitchell <jrmitche@puck.nether.net>
To: =?iso-8859-1?Q?Vitkovsk=FD?= Adam <adam.vitkovsky@swan.sk>
Subject: Re: WG review for draft-lapukhov-bgp-routing-large-dc
Message-ID: <20141021025005.GA20727@puck.nether.net>
References: <3F437107848A5140A6A19222EFFB34811FC80399@PRN-MBX01-2.TheFacebook.com> <20194_1406558343_53D66086_20194_232_1_53C29892C857584299CBF5D05346208A07192B00@PEXCVZYM11.corporate.adroot.infra.ftgroup> <2E4BB27CAB87BF43B4207C0E55860F18162671@eusaamb103.ericsson.se> <20140729094234.GB19231@juniper.net> <2E4BB27CAB87BF43B4207C0E55860F18162EFD@eusaamb103.ericsson.se> <CAG4d1rcNFK1QFR=+q1zPziWnKCoO34szd0qWpqUj7vhA4N-EXg@mail.gmail.com> <3F437107848A5140A6A19222EFFB34811FC81FE8@PRN-MBX01-2.TheFacebook.com> <CFFD1091.6B280%jeff.tantsura@ericsson.com> <3F437107848A5140A6A19222EFFB34811FC8305B@PRN-MBX01-2.TheFacebook.com> <61DC6BC4ABA10E4489D4A73EBABAC18B02388375@EX01.swan.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <61DC6BC4ABA10E4489D4A73EBABAC18B02388375@EX01.swan.local>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.7 (puck.nether.net [127.0.0.1]); Mon, 20 Oct 2014 22:50:08 -0400 (EDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/jAoR2oN7qwvOTzJEKQZM6-BuqfM
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 Oct 2014 02:51:51 -0000

Inline ...

-Jon

On 31/07/14 09:48 +0000, Vitkovský Adam wrote:
> Hello Peter,
> 
> I'd like to ask couple of questions regarding the design and confirm my understanding please. 
> 
> 
> What is the recommended fan out ratio for Tier3 to Tier2 and Tier2 to Tier1 please? 
> Tier3 to Tier2 would be 1/4 (so in case one Tier2 device fails the remaining BW still available for a cluster is 75%) (Tier3 device has 4 ECMP paths). 
> Tier2 to Tier1 would be 1/2 (so in case one Tier1 device fails the remaining BW still available for cluster is 87.5%) (Tier2 device has 2 ECMP paths). 
> 
> Or is it more like 1/32 for the Tier3 to Tier2 (Tier3 device has 32 ECMP paths) please?  

This is highly dependent on maximum size (# of clusters) in the DC and
amount of traffic required to be carried between tiers.  YMMV.  If Tier3
in your design is a 64 port TOR, it may be a bit extreme to utilize half
the ports as uplinks, although certainly it is possible.  Most cluster
designs may choose 1/4 or 1/8 but higher is certainly possible.  Making
a recommendation that applies to all DC size and traffic requirements is
probably not feasible.

> 
> 
> 8.2.1. Collapsing Tier-1 Devices Layer. 
>  - I think that as a result of collapsing the number of Tier1 devices to a 1/2 the impact of the failure of a single Tier1 device will increase in 50%. 
>  - Thus wouldn't it be more desirable to leave the same number of Tier1 devices and only add links from a particular tier2 device to another/neighboring pair of Tier1 devices please? 
>  - The reduction in port capacity would remain the same. 
>  - However the impact of a failure of a single link or single Tier1 device is unchanged. 
> 
> 
> 
> 8.2. Route Summarization within Clos Topology. 
>  - Since you have mentioned that all the devices are preferably of the same type to accommodate REQ2. 
>  - I'm thinking they would probably have the same FIB capacity right please? 
>  - So if Tier1 device can hold all the DC routes than Tier2 and Tier3 devices can as well right? 
>  - If the FIB size differs between the devices used in various Tiers than summarization is beneficial indeed. 

I think you read these sections as disjoint.  The only purpose of
section 8.2.1 is if you desire to do summarization in the Clos, most
operators may agree the trade-off is not worth it and not summarize in
the fabric.  These operators may also have the same FIB capacity on all
devices.  Other operators may desire summarization in the Clos due to
not selecting devices of same FIB capacity or wanting to reduce the
control plane exposure as suggested in section 8.2.  8.2.1 explains one
way that could be done and the associated trade-offs of doing it.

> 
> If FIB size is a cause for concern would it be possible to utilize a scheme where servers are grouped into server groups, then to define which server groups need to communicate with other set of server groups or everybody or the internet please? 
> This way prefixes could be marked and filters on Tier3 and Tier 2 devices set accordingly -to only allow the necessary prefixes to be accepted form a Peer or inserted from BGP into RIB/FIB. 
> Drawback is of course the increased operational complexity maintaining filters as well as troubleshooting. 
> Though with clear server groups to Tier3 devices (or clusters) mapping scheme the filters would be set once than maintained only occasionally. 
> Also with a clear communities scheme troubleshooting would be straight forward I believe. 
> 
> I'm thinking like in MPLS VRFs if a particular PE (Tier3 device) is serving only a subset of VRFs(server groups) it doesn't really need to hold all the DC routes. 

Implicit in the requirements is full reachability to server subnets in
the design (from every other server subnet and typically with default
providing external connectivity to the CloS as outlined).  If this is
not a requirement, an alternative would be not building a large scale
CloS network but rather build a number of small scale CloS networks that
are custom built to such server groups.  Obviously this limits the
fungability of the equipment deployed.  Also, it should be stated that
operational simplicity is a stated goal of this design.

> 
> 
> 8.3. ICMP Unreachable Message Masquerading. 
>  Another option is to make the network device perform IP address
>  masquerading, 
>  - Does that mean the network device will respond with RID/Loopback IP during traceroute please? 
>  - If so it would be than impossible to pinpoint the link used to forward traffic to the next hop so if there are two IP paths between directly connected devices we wouldn't be able to distinguish the failed one. 
>  - But I guess this kind of setup is not going to be used. 

Yes, typically there is only one connection in the design between two
specific devices in different Tiers, so if the previous hop responded
and the device respond where TTL is exceeded has source of RID, this is
effectively identifying the link.  Sometimes there is more than one
link, but in those cases, at times the operator may be using LAG, making
this valid as well.  All of section 8 is options to the design - if the
specific design an operator chooses has multiple non-LAG links between
two device in seperate tiers, and traceroute response is deemed highly
useful, they may opt for the second option of section 5.2.3 rather than
icmp masquerading.

> 
> 
> 
> And just some nit picking. 
> 7.1. Fault Detection Timing. 
> This feature is sometimes called as "fast fallover" 
>  - Do you mean the "fast external failover" as it only applies to eBGP sessions? 
>  - Or you mean the "fast peering session deactivation" functionality that brings the same functionality to iBGP sessions please? 

It means the first, although more implementations use the word fallover
not failover in the command.  If it is confusing we can add external to
the wording.  This entire draft is about EBGP only design, so the second
does not apply.


From nobody Tue Oct 21 11:38:41 2014
Return-Path: <fred@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D7A1A1BCA for <rtgwg@ietfa.amsl.com>; Tue, 21 Oct 2014 11:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 9zp05Mc2eAOG for <rtgwg@ietfa.amsl.com>; Tue, 21 Oct 2014 11:38:38 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C50A31A6F62 for <rtgwg@ietf.org>; Tue, 21 Oct 2014 11:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2433; q=dns/txt; s=iport; t=1413916717; x=1415126317; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=7UiuV6yglodxL01QPhbOhKdWIpeTmc5fJwD7HCP3JEM=; b=NoVG7Lp6qaN6sVuGkFbl0XwW5jRiyRV40D/9mbcphGJAEONv3ukW5kFO 06dHOAMjdwJkVvLfZWWT8cp2yBzD2wuQFnGKq8HR+6JABOXI6ocFsJg7f kXozndXbNb0TIMIHT+gw0gAn9BYIOjj6ZcpzD6XTgO6n1EV+X5+Oz/eQy c=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFAJenRlStJV2c/2dsb2JhbABcgw5TWATMcQyHSwKBFRYBcguEAwEBAwEBAQFrCxACAQhGJwslAgQOBQkFiCkIDcYGAQEBAQEBAQEBAQEBAQEBAQEBAQEBF5BXAgUJgySBHgWSAYIOgVBohxOBMDyDDIpVhliDeGwBgUeBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,763,1406592000";  d="asc'?scan'208";a="89089062"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP; 21 Oct 2014 18:38:37 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s9LIcbfJ019178 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Oct 2014 18:38:37 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.152]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Tue, 21 Oct 2014 13:38:36 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: I-D Action: draft-baker-rtgwg-src-dst-routing-use-cases-01.txt
Thread-Topic: I-D Action: draft-baker-rtgwg-src-dst-routing-use-cases-01.txt
Thread-Index: AQHP7V3WNoYSOFeG0UmmRufhKzssPZw7NYeA
Date: Tue, 21 Oct 2014 18:38:36 +0000
Message-ID: <82477361-247F-4278-A247-774CA35510CB@cisco.com>
References: <20141021183527.3465.75047.idtracker@ietfa.amsl.com>
In-Reply-To: <20141021183527.3465.75047.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.155.136.160]
Content-Type: multipart/signed; boundary="Apple-Mail=_FC4A7324-6BFD-4703-884B-4DF8BEDBE36B"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/PHao8hv3f6go3aORMwXxe7zeM3Q
Cc: David Lamparter <david@opensourcerouting.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 Oct 2014 18:38:40 -0000

--Apple-Mail=_FC4A7324-6BFD-4703-884B-4DF8BEDBE36B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

This is a simple repost of the -00 version of the draft. We may get an =
updated version out. But this is there is support of David=92s work in =
IS-IS on source/destination routing.

On Oct 21, 2014, at 11:35 AM, <internet-drafts@ietf.org> =
<internet-drafts@ietf.org> wrote:

>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>=20
>=20
>        Title           : Requirements and Use Cases for =
Source/Destination Routing
>        Author          : Fred Baker
> 	Filename        : =
draft-baker-rtgwg-src-dst-routing-use-cases-01.txt
> 	Pages           : 10
> 	Date            : 2014-10-21
>=20
> Abstract:
>   This note attempts to capture important use cases for source/
>   destination routing.
>=20
>=20
> The IETF datatracker status page for this draft is:
> =
https://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-cas=
es/
>=20
> There's also a htmlized version available at:
> =
http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases-01
>=20
> A diff from the previous version is available at:
> =
http://www.ietf.org/rfcdiff?url2=3Ddraft-baker-rtgwg-src-dst-routing-use-c=
ases-01
>=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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--Apple-Mail=_FC4A7324-6BFD-4703-884B-4DF8BEDBE36B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFURqgrbjEdbHIsm0MRAvEhAKDlmwx0zQuxJ3uE5m1c40L/XvEOkACgkCXk
jLJkN8xzyAWBKxjmM1DojYo=
=XVRP
-----END PGP SIGNATURE-----

--Apple-Mail=_FC4A7324-6BFD-4703-884B-4DF8BEDBE36B--


From nobody Wed Oct 22 12:07:53 2014
Return-Path: <equinox@diac24.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E52E71AD2AF; Wed, 22 Oct 2014 12:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 l_6UU3qIjhxy; Wed, 22 Oct 2014 12:07:35 -0700 (PDT)
Received: from spaceboyz.net (spaceboyz.net [IPv6:2001:8d8:870:1000::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926B91AD333; Wed, 22 Oct 2014 12:07:11 -0700 (PDT)
Received: from [2001:8d8:870:10ef:1::] (helo=jupiter.n2.diac24.net) by spaceboyz.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from <equinox@diac24.net>) id 1Xh1FT-0007ua-Cj; Wed, 22 Oct 2014 21:07:07 +0200
Received: from equinox by jupiter.n2.diac24.net with local (Exim 4.82) (envelope-from <equinox@diac24.net>) id 1Xh1FF-001Iey-Ls; Wed, 22 Oct 2014 21:06:56 +0200
Date: Wed, 22 Oct 2014 21:06:53 +0200
From: David Lamparter <equinox@diac24.net>
To: rtgwg@ietf.org, homenet@ietf.org
Subject: Re: dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141022190653.GB868521@jupiter.n2.diac24.net>
References: <20141020204033.GD236844@jupiter.n2.diac24.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20141020204033.GD236844@jupiter.n2.diac24.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/qbcJ2g54UEMl4H7c56UggoMQxnM
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 22 Oct 2014 19:07:41 -0000

On Mon, Oct 20, 2014 at 10:40:33PM +0200, David Lamparter wrote:
> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-qualifiers/?include_text=1
> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?include_text=1

rtgwg & homenet:

So, these drafts describe the general router behaviour for D/S, without
heading into homenet specifics.  There are a few points that might be
worth going into detail:

- the first draft describes adding random kinds of attributes into route
  lookup.  That's very generic, and it didn't add significant
  complexity, but I don't think we're expecting to insert things in the
  middle?

- we haven't discussed some of the boundaries to other functions.
  Recursive route handling is unlikely to be relevant for homenet, but
  might warrant feedback from rtgwg.  And the situation is rather
  complex, the draft has an open "multiple-choices TBD" there.

  Interesting for both rtgwg & homenet are behaviour with uRPF filtering
  and multicast RP lookups.  The draft says:
   for uRPF, flip dst & src and match both, if the system supports it.
     If it doesn't, match packet source against all possible route dst.
     (This probably needs better wording in the draft)
   for mcast reverse-path lookup, ignore all D/S routes.  Multicast has
     only (group, source) available, no destination to match against the
     route source prefix.

So, to be explicit on this, D/S routing is conceptually incompatible
with multicast reverse path lookups.  But that can be dealt with (cue to
homenet multicast discussion here.)


Hoping for feedback (including, possibly, "I don't care" or "I have no
opinion"),


-David


P.S.: there is an unfortunate scheduling collision between homenet and
rtgwg for IETF 91... please convert to mail as much as possible!


From nobody Wed Oct 22 13:16:33 2014
Return-Path: <fred@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81D391A1AA5; Wed, 22 Oct 2014 13:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 T6tPvnXMwHRy; Wed, 22 Oct 2014 13:16:30 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6D6C1A1A29; Wed, 22 Oct 2014 13:16:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1837; q=dns/txt; s=iport; t=1414008991; x=1415218591; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oaa7DHsMvz0K+jXrxo6QJ+3w4xp7MZrT12KJmCtmiQU=; b=Gldb//oMUIIhObHznDVRESoUZKt/DLYAH+OGe2mkYYRkq/2/jcBJOAwd Byz0uvwGRklOvVdQMYzB9dIN0/yt5RT71/ElgX4kbn4JnRp6Wspe9EsMC 3VHAMHVX2IfwGXhqKUxkYKfif8ozdNAeGqfLWY2pcv7KvVjASi+NG68lu o=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFANAPSFStJV2P/2dsb2JhbABcgw5UWATMX4dLAoEOFgF9hAIBAQEDAXkFCwIBCA4KLjIlAgQOBQ4NiB0IDcVuAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSQVweDLYEeBZIEgg6BUGiHE5Yqg3hsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,770,1406592000";  d="asc'?scan'208";a="89462280"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-2.cisco.com with ESMTP; 22 Oct 2014 20:16:30 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9MKGTB4006838 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Oct 2014 20:16:30 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.248]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Wed, 22 Oct 2014 15:16:29 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: David Lamparter <equinox@diac24.net>
Subject: Re: dst/src routing drafts (for IETF-91 rtgwg)
Thread-Topic: dst/src routing drafts (for IETF-91 rtgwg)
Thread-Index: AQHP7KYr8Fy7zf5Z70yFtC9ToRE4KA==
Date: Wed, 22 Oct 2014 20:16:29 +0000
Message-ID: <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net>
In-Reply-To: <20141022190653.GB868521@jupiter.n2.diac24.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.118]
Content-Type: multipart/signed; boundary="Apple-Mail=_A342AF8E-5ABC-4A62-AE96-CFC74460E806"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/a1TMcFbQzCzX1i0Z0jPVTkNq7y0
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 22 Oct 2014 20:16:32 -0000

--Apple-Mail=_A342AF8E-5ABC-4A62-AE96-CFC74460E806
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 22, 2014, at 12:06 PM, David Lamparter <equinox@diac24.net> =
wrote:

> On Mon, Oct 20, 2014 at 10:40:33PM +0200, David Lamparter wrote:
>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-quali=
fiers/?include_text=3D1
>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?in=
clude_text=3D1

Speaking strictly for myself, I=92m not sure why homenet is relevant. =
The technology is related to networks that have different routing depend =
on on one=92s use case. A class of solutions for it has been called the =
=93fish=94 problem, and built using multi-topology routing. In homenet, =
it=92s called SADR, and is primarily about egress routing (routing to an =
egress to an upstream ISP that gave you a PA prefix). While one doesn=92t =
really want to confuse theory with practice, in theory it could be used =
between points of a network, to prevent folks using one set of prefixes =
to talk with another set, or to force routing of some sessions in some =
ways.

Personally, those are a class of problems I associate with campus =
networks more than residential networks.

--Apple-Mail=_A342AF8E-5ABC-4A62-AE96-CFC74460E806
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUSBCbbjEdbHIsm0MRAt9VAJwO7TWL/GoPRxUSxtF2umu95xwdXQCg2yGw
YhppcpRpkls65fus2i41JQw=
=mb3/
-----END PGP SIGNATURE-----

--Apple-Mail=_A342AF8E-5ABC-4A62-AE96-CFC74460E806--


From nobody Fri Oct 24 16:57:11 2014
Return-Path: <aretana@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6531A1BE3 for <rtgwg@ietfa.amsl.com>; Fri, 24 Oct 2014 16:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 dhHDedcwXN4I for <rtgwg@ietfa.amsl.com>; Fri, 24 Oct 2014 16:57:08 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C14C41A1ACA for <rtgwg@ietf.org>; Fri, 24 Oct 2014 16:57:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=238; q=dns/txt; s=iport; t=1414195028; x=1415404628; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ju/DuYBuedxMbIh+0fXjPD1wj9r4FqnJfvuyNpTyRg4=; b=i73jYTvMCvxDeIS07Oc+EWUOgBaxbnX2hKi1s1J0GZwlBk2IjOB79s6p Rcw46d0W3YtJ4XngQ6t+f1hrlhcg8dOoxB3TLxrubTEHR8yUFk+utV+B8 Fzz0YNWlZPH0G86u3Ikhu3yqxSSYEQIfhaS/im5/fAaLCNUuShVQoDxcR 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAN/mSlStJA2D/2dsb2JhbABcgw6BLASNXsccAoEGFgF9hAMBAQQ6PxACAQgOKBAyJQIEAQ0FiEHKOgEBAQEBAQEBAQEBAQEBAQEBAQEBAReQWAeESwEEj2eCHotYliyDeGyBSIEDAQEB
X-IronPort-AV: E=Sophos;i="5.04,783,1406592000"; d="scan'208";a="366504976"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-2.cisco.com with ESMTP; 24 Oct 2014 23:57:00 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9ONv0FC022634 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 23:57:00 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.162]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 18:57:00 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: David Lamparter <equinox@diac24.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: dst/src routing drafts (for IETF-91 rtgwg)
Thread-Topic: dst/src routing drafts (for IETF-91 rtgwg)
Thread-Index: AQHP7KYnLGSFMgC+0k+iplO05ZsGGJxAA9sA
Date: Fri, 24 Oct 2014 23:56:59 +0000
Message-ID: <D0705F68.72BCB%aretana@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net>
In-Reply-To: <20141020204033.GD236844@jupiter.n2.diac24.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.217.171]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11EC1DE5AA0ADA488590B31819E6AB18@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/7CNI-fW3YH7KEqiNNR7fub1D6SA
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 24 Oct 2014 23:57:10 -0000

On 10/20/14, 4:40 PM, "David Lamparter" <equinox@diac24.net> wrote:

>Last but not least, I'd like to request a slot at the IETF 91 rtgwg
>meeting to present these drafts.

David:

How much time do you want?

Thanks!

Alvaro.


From nobody Mon Oct 27 10:09:49 2014
Return-Path: <psarkar@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3511A6F3A for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 10:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 IH8mSFLhduBC for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 10:09:40 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0122.outbound.protection.outlook.com [207.46.100.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88D071A3B9D for <rtgwg@ietf.org>; Mon, 27 Oct 2014 10:09:28 -0700 (PDT)
Received: from BN1PR05MB520.namprd05.prod.outlook.com (10.141.65.151) by BN1PR05MB517.namprd05.prod.outlook.com (10.141.65.142) with Microsoft SMTP Server (TLS) id 15.1.6.9; Mon, 27 Oct 2014 17:09:27 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.84]) by BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.84]) with mapi id 15.01.0006.000; Mon, 27 Oct 2014 17:09:27 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-psarkar-rtgwg-multihomed-prefix-lfa-00.txt
Thread-Topic: New Version Notification for draft-psarkar-rtgwg-multihomed-prefix-lfa-00.txt
Thread-Index: AQHP8gjD9FrPxCvTrEy2VDmmfNy3tw==
Date: Mon, 27 Oct 2014 17:09:26 +0000
Message-ID: <D07479DA.16185%psarkar@juniper.net>
References: <20141027170709.6777.50475.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027170709.6777.50475.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.4.5.141003
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [116.197.184.15]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB517;
x-forefront-prvs: 0377802854
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(199003)(189002)(51704005)(479174003)(377424004)(377454003)(106356001)(120916001)(64706001)(106116001)(105586002)(21056001)(46102003)(99396003)(80022003)(101416001)(99286002)(66066001)(20776003)(76482002)(107046002)(77096002)(107886001)(2351001)(85306004)(95666004)(97736003)(36756003)(2501002)(110136001)(230783001)(83506001)(15975445006)(40100003)(122556002)(92566001)(4396001)(19580405001)(85852003)(92726001)(87936001)(2656002)(31966008)(86362001)(15202345003)(76176999)(50986999)(54356999)(19580395003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB517; H:BN1PR05MB520.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BEE3797C6EE3D84DB7172FD3562EE1F7@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/oq7PmevF3hZVSiZY0nVd7aA9WrU
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 Oct 2014 17:09:43 -0000

Hi RTGWG members,

Please comment and provide your feedback.

Thanks and Regards,
-Pushpasis

On 10/27/14, 10:37 PM, "internet-drafts@ietf.org"
<internet-drafts@ietf.org> wrote:

>
>A new version of I-D, draft-psarkar-rtgwg-multihomed-prefix-lfa-00.txt
>has been successfully submitted by Pushpasis Sarkar and posted to the
>IETF repository.
>
>Name:		draft-psarkar-rtgwg-multihomed-prefix-lfa
>Revision:	00
>Title:		LFA selection for Multi-Homed Prefixes
>Document date:	2014-10-27
>Group:		Individual Submission
>Pages:		9
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-psarkar-rtgwg-multihomed-prefix-
>lfa-00.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-psarkar-rtgwg-multihomed-prefix-lfa
>/
>Htmlized:      =20
>http://tools.ietf.org/html/draft-psarkar-rtgwg-multihomed-prefix-lfa-00
>
>
>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 neighbours as a potential alternates for multi-homed
>   prefixes.  It also provides detailed criteria for evaluating
>   potential alternates for external prefixes advertised by OSPF ASBRs.
>
>
>                 =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 Mon Oct 27 14:55:29 2014
Return-Path: <aretana@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF9041A01EC for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 14:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 SN3Tkp1fxX9h for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 14:55:24 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4205C1A011F for <rtgwg@ietf.org>; Mon, 27 Oct 2014 14:54:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1677; q=dns/txt; s=iport; t=1414446875; x=1415656475; h=from:to:cc:subject:date:message-id:mime-version; bh=G4z3d4GtuuroFTktaSku3Q0MsEPwK+x4amjDgIrZzno=; b=XN4jX3nfRy91DnWxaCvX1WhZLMfzpr8VhQe6Ow0CgmYKQC6zdBCki1Vl hUrXE557NDHUUrlbuvZGgBaGOorc06IZdjVt8TEt48m/KQ904+K0tXU2R w9l6fhCX2JXJjcHINK7rgGmLxj8k50di/hB/Tg4nsvCrfsAT+wI/6Nj6A I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFABy+TlStJV2T/2dsb2JhbABcgkhGVFkDzVCHTYEdFgFyC4N5EHkSAQsBdCcEDg6IOA3LbwEBAQcBAQEBAQEckQiEUgWPaYIei1qWLoN4gjSBAwEBAQ
X-IronPort-AV: E=Sophos; i="5.04,798,1406592000"; d="scan'208,217"; a="90809981"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP; 27 Oct 2014 21:54:34 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9RLsYt9024940 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Oct 2014 21:54:34 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.162]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Mon, 27 Oct 2014 16:54:34 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: IETF 91 Draft Agenda (rtgwg)
Thread-Topic: IETF 91 Draft Agenda (rtgwg)
Thread-Index: AQHP8jCYYVaNgvtMJUOPXxZz4aLGEw==
Date: Mon, 27 Oct 2014 21:54:34 +0000
Message-ID: <D0744567.731AC%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.254.239]
Content-Type: multipart/alternative; boundary="_000_D0744567731ACaretanaciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/wJ8z6-UVGoQhGqfS607ludMKg2c
Cc: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 Oct 2014 21:55:26 -0000

--_000_D0744567731ACaretanaciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

HI!

I just published the draft agenda:  http://www.ietf.org/proceedings/91/agen=
da/agenda-91-rtgwg

We still have plenty of meeting time for other requests.. In a couple of ca=
ses we still haven=92t settled on the topic, so I didn=92t include you.

Note that the final agenda has to be in on Nov/3.  Let me know if I missed =
any request.

Thanks!

Alvaro.

--_000_D0744567731ACaretanaciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <E34F4F3FDE3ABB49A1672FDDDD19066E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>HI!</div>
<div><br>
</div>
<div>I just published the draft agenda: &nbsp;<a href=3D"http://www.ietf.or=
g/proceedings/91/agenda/agenda-91-rtgwg">http://www.ietf.org/proceedings/91=
/agenda/agenda-91-rtgwg</a></div>
<div><br>
</div>
<div>We still have plenty of meeting time for other requests.. In a couple =
of cases we still haven=92t settled on the topic, so I didn=92t include you=
.</div>
<div><br>
</div>
<div>Note that the final agenda has to be in on Nov/3. &nbsp;Let me know if=
 I missed any request.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
</body>
</html>

--_000_D0744567731ACaretanaciscocom_--


From nobody Mon Oct 27 18:53:09 2014
Return-Path: <liu.bin21@zte.com.cn>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CB11A026A for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 18:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.956
X-Spam-Level: 
X-Spam-Status: No, score=-101.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RDNS_NONE=0.793, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fauydhs3nhx9 for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 18:53:05 -0700 (PDT)
Received: from mx5.zte.com.cn (unknown [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 13C141A0233 for <rtgwg@ietf.org>; Mon, 27 Oct 2014 18:53:05 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id DA385123B717; Tue, 28 Oct 2014 09:52:55 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id s9S1qnIY017752; Tue, 28 Oct 2014 09:52:49 +0800 (GMT-8) (envelope-from liu.bin21@zte.com.cn)
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Soliciting comments for new version for draft-sl-rtgwg-far-dcn-02.txt
MIME-Version: 1.0
Importance: High
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OFE7BFEACC.8EDCA767-ON48257D7F.0008F35D-48257D7F.000A6862@zte.com.cn>
From: liu.bin21@zte.com.cn
Date: Tue, 28 Oct 2014 09:52:49 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2014-10-28 09:52:33, Serialize complete at 2014-10-28 09:52:33
Content-Type: multipart/alternative; boundary="=_alternative 000A686148257D7F_="
X-MAIL: mse01.zte.com.cn s9S1qnIY017752
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/oIjycC6Dvj_qSd7ijBKWckrfRPU
Cc: ytsun@bjtu.edu.cn, bhumip.khasnabish@zteusa.com
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 01:53:07 -0000

This is a multipart message in MIME format.
--=_alternative 000A686148257D7F_=
Content-Type: text/plain; charset="US-ASCII"

Greeting all,

We updated the far draft with 02 version, and we hope to get valuable 
comments of experts in the routing group on our draft. 

Best regards, 
Richard Bin Liu 


A new version of I-D, draft-sl-rtgwg-far-dcn-02.txt
has been successfully submitted by Bin Liu and posted to the
IETF repository.

Name:                            draft-sl-rtgwg-far-dcn
Revision:                02
Title:                           Generic Fault-avoidance Routing Protocol 
for Data Center Networks
Document date:           2014-10-27
Group:                           Individual Submission
Pages:                           30
URL:            
http://www.ietf.org/internet-drafts/draft-sl-rtgwg-far-dcn-02.txt
Status:         https://datatracker.ietf.org/doc/draft-sl-rtgwg-far-dcn/
Htmlized:       http://tools.ietf.org/html/draft-sl-rtgwg-far-dcn-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-sl-rtgwg-far-dcn-02

Abstract:
   This draft proposes a generic routing method and protocol for a
   regular data center network, named as the fault-avoidance routing
   (FAR) protocol.  FAR protocol provides a generic routing method for
   all types of network architectures that are proposed for large-scale
   cloud-based data centers over the past few years.  FAR protocol is
   well designed to fully leverage the regularity in the topology and
   compute its routing table in a simplistic manner.  Fat-tree is taken
   as an example architecture to illustrate how FAR protocol can be
   applied in real operational scenarios.

--=_alternative 000A686148257D7F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Greeting all,</font>
<br>
<br><font size=2 face="sans-serif">We updated the far draft with 02 version,
and we hope to get valuable comments of experts in the routing group on
our draft. </font>
<br>
<br><font size=2 face="sans-serif">Best regards, </font>
<br><font size=2 face="sans-serif">Richard Bin Liu </font>
<br>
<br><tt><font size=2><br>
A new version of I-D, draft-sl-rtgwg-far-dcn-02.txt<br>
has been successfully submitted by Bin Liu and posted to the<br>
IETF repository.<br>
<br>
Name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-sl-rtgwg-far-dcn<br>
Revision: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
02<br>
Title: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Generic
Fault-avoidance Routing Protocol for Data Center Networks<br>
Document date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; 2014-10-27<br>
Group: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Individual
Submission<br>
Pages: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;30<br>
URL: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;http://www.ietf.org/internet-drafts/draft-sl-rtgwg-far-dcn-02.txt<br>
Status: &nbsp; &nbsp; &nbsp; &nbsp; https://datatracker.ietf.org/doc/draft-sl-rtgwg-far-dcn/<br>
Htmlized: &nbsp; &nbsp; &nbsp; http://tools.ietf.org/html/draft-sl-rtgwg-far-dcn-02<br>
Diff: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; http://www.ietf.org/rfcdiff?url2=draft-sl-rtgwg-far-dcn-02<br>
<br>
Abstract:<br>
 &nbsp; This draft proposes a generic routing method and protocol for a<br>
 &nbsp; regular data center network, named as the fault-avoidance routing<br>
 &nbsp; (FAR) protocol. &nbsp;FAR protocol provides a generic routing method
for<br>
 &nbsp; all types of network architectures that are proposed for large-scale<br>
 &nbsp; cloud-based data centers over the past few years. &nbsp;FAR protocol
is<br>
 &nbsp; well designed to fully leverage the regularity in the topology
and<br>
 &nbsp; compute its routing table in a simplistic manner. &nbsp;Fat-tree
is taken<br>
 &nbsp; as an example architecture to illustrate how FAR protocol can be<br>
 &nbsp; applied in real operational scenarios.<br>
</font></tt>
--=_alternative 000A686148257D7F_=--


From nobody Mon Oct 27 20:53:30 2014
Return-Path: <william.atwood@concordia.ca>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EE01A049A for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 20:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.245
X-Spam-Level: 
X-Spam-Status: No, score=-1.245 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaATG0udAtyJ for <rtgwg@ietfa.amsl.com>; Mon, 27 Oct 2014 20:53:25 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.92]) by ietfa.amsl.com (Postfix) with ESMTP id B86D11A01E5 for <rtgwg@ietf.org>; Mon, 27 Oct 2014 20:53:25 -0700 (PDT)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id s9S3rOct021603;  Mon, 27 Oct 2014 23:53:24 -0400
Message-ID: <544F1334.4020301@concordia.ca>
Date: Mon, 27 Oct 2014 23:53:24 -0400
From: William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Fwd: New Version Notification for draft-atwood-rtgwg-secure-rtg-00.txt
References: <20141027225211.27909.12269.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027225211.27909.12269.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20141027225211.27909.12269.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2014-10-27 23:53:24 EDT
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/mYC0DtGwaBvpYQfWY-Q9sY2p_58
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 03:53:28 -0000

We have posted draft-atwood-rtgwg-secure-rtg, and requested a slot to
present it in Hawaii.  We solicit comments from the working group.

We consider routing from the perspective of four layers:
1 Routing Protocol           (exchange of routing packets)
2 Keys and Security Protocol (how to provide authentication
                             and integrity)
3 Key and Security Association Management
                             (how to negotiate the keys that
                             will be used)
4 Configuration Management   (how to push the parameters for
                             Layer 3 onto the router)

Many routing protocols are defined (layer 1).
Many routing protocols have a security option defined in their
specification (layer 2).
Some key negotiation protocols have been proposed, but no method for
conveniently managing them has been put forth (layer 3).
No work has been done (to our knowledge) specifically on configuring
security for routing protocols (general configuration approaches clearly
exist) (layer 4).

We use the Crypto-Key-Table (CKT) defined in RFC 7210.  We define two
additional databases, the Router Security Parameter Database (RSPD) and
the Router Peer Authorization Database (RPAD).  Together these form the
Routing Protocol Security (RPsec) framework.

We have defined YANG modules to correspond to the contents of the CKT,
the RSPD and the RPAD.  Version -00 of the draft contains most of the
motivation.  Version -01 will contain details of the proposed RSPD and
RPAD contents, along with the YANG models.

We believe that this will enable no-hands-on (after initial
configuration) routing protocol security, with configurable key hygiene.

Comments from the community will be most welcome.

Bill Atwood
Nitin Prajapati



-------- Original Message --------
Subject: New Version Notification for draft-atwood-rtgwg-secure-rtg-00.txt
Date: Mon, 27 Oct 2014 15:52:11 -0700
From: <internet-drafts@ietf.org>
To: William Atwood <william.atwood@concordia.ca>, Nitin Prajapati
<prajapatinitin@hotmail.com>, "J. William Atwood"
<william.atwood@concordia.ca>, Nitin Prajapati <prajapatinitin@hotmail.com>


A new version of I-D, draft-atwood-rtgwg-secure-rtg-00.txt
has been successfully submitted by William Atwood and posted to the
IETF repository.

Name:		draft-atwood-rtgwg-secure-rtg
Revision:	00
Title:		A Framework for Secure Routing Protocols
Document date:	2014-10-27
Group:		Individual Submission
Pages:		9
URL:
http://www.ietf.org/internet-drafts/draft-atwood-rtgwg-secure-rtg-00.txt
Status:
https://datatracker.ietf.org/doc/draft-atwood-rtgwg-secure-rtg/
Htmlized:       http://tools.ietf.org/html/draft-atwood-rtgwg-secure-rtg-00


Abstract:
   When tightening the security of the core routing infrastructure, two
   steps are necessary.  The first is to secure the routing protocols'
   packets on the wire.  The second is to ensure that the keying
   material for the routing protocol exchanges is distributed only to
   the appropriate routers.  This document specifies a way of organizing
   the security parameters and a method for conveniently controlling
   those parameters using YANG and NETCONF.





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 Tue Oct 28 08:52:04 2014
Return-Path: <lucy.yong@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBC6E1A8BBF for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 08:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 CA8VtSLtJDAb for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 08:51:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552E61A8BAF for <rtgwg@ietf.org>; Tue, 28 Oct 2014 08:51:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOD39333; Tue, 28 Oct 2014 15:51:46 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 28 Oct 2014 15:51:31 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0158.001; Tue, 28 Oct 2014 08:51:18 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-yong-rtgwg-igp-multicast-arch-00.txt
Thread-Topic: New Version Notification for draft-yong-rtgwg-igp-multicast-arch-00.txt
Thread-Index: AQHP8jCa/ULp39sgAUeTdVhby85KaZxFp2Cg
Date: Tue, 28 Oct 2014 15:51:18 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D453FED56@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.148.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/-uBtc7foa7R2kRDX9y7qRDjKM6A
Cc: "draft-yong-rtgwg-igp-multicast-arch@tools.ietf.org" <draft-yong-rtgwg-igp-multicast-arch@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 15:51:56 -0000

SGVsbG8sDQoNCldlIHVwbG9hZCB0aGlzIG5ldyBkcmFmdCBhbmQgbGlrZSB0byBnZXQgeW91ciBj
b21tZW50cy4NCg0KVGhlIHN1YmplY3Qgd2FzIHByb3Bvc2VkIHRvIElTLUlTIFdHIGZpcnN0LiBB
RCBzdWdnZXN0ZWQgc3BsaXR0aW5nIHRoZSBvcmlnaW5hbCBwcm9wb3NhbCBpbnRvIHR3bzogSUdQ
IG11bHRpY2FzdCBhcmNoaXRlY3R1cmUgYW5kIElTLUlTIHByb3RvY29sIGV4dGVuc2lvbiwgYW5k
IHdvcmsgb3V0IHRoZSBhcmNoaXRlY3R1cmUgaW4gUlRHIFdHLiANCg0KV2Ugd2lsbCBwcmVzZW50
IHRoaXMgaW4gSG9ub2x1bHUuDQoNClRoYW5rcywNCkx1Y3kNCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0
LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBNb25kYXksIE9jdG9iZXIgMjcsIDIwMTQgNDo1NCBQ
TQ0KVG86IEFuZHJldyBRdTsgSm9uIEh1ZHNvbjsgTHVjeSB5b25nOyBIYW93ZWlndW87IEx1Y3kg
eW9uZzsgRG9uYWxkIEVhc3RsYWtlOyBBbmRyZXcgUXU7IERvbmFsZCBFLiBFYXN0bGFrZSAzcmQ7
IEpvbiBIdWRzb247IEhhb3dlaWd1bw0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9u
IGZvciBkcmFmdC15b25nLXJ0Z3dnLWlncC1tdWx0aWNhc3QtYXJjaC0wMC50eHQNCg0KDQpBIG5l
dyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQteW9uZy1ydGd3Zy1pZ3AtbXVsdGljYXN0LWFyY2gtMDAu
dHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEx1Y3kgWW9uZyBhbmQgcG9z
dGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCk5hbWU6CQlkcmFmdC15b25nLXJ0Z3dnLWln
cC1tdWx0aWNhc3QtYXJjaA0KUmV2aXNpb246CTAwDQpUaXRsZToJCUlHUCBNdWx0aWNhc3QgQXJj
aGl0ZWN0dXJlDQpEb2N1bWVudCBkYXRlOgkyMDE0LTEwLTI3DQpHcm91cDoJCUluZGl2aWR1YWwg
U3VibWlzc2lvbg0KUGFnZXM6CQkxMw0KVVJMOiAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5v
cmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXlvbmctcnRnd2ctaWdwLW11bHRpY2FzdC1hcmNoLTAw
LnR4dA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LXlvbmctcnRnd2ctaWdwLW11bHRpY2FzdC1hcmNoLw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXlvbmctcnRnd2ctaWdwLW11bHRpY2FzdC1hcmNo
LTAwDQoNCg0KQWJzdHJhY3Q6DQpUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBJbnRlcmlvciBHYXRl
d2F5IFByb3RvY29sIChJR1ApIG5ldHdvcmsgYXJjaGl0ZWN0dXJlIHRvIHN1cHBvcnQgbXVsdGlj
YXN0IHRyYW5zcG9ydC4gSXQgZGVzY3JpYmVzIHRoZSBhcmNoaXRlY3R1cmUgY29tcG9uZW50cyBh
bmQgdGhlIGFsZ29yaXRobXMgdG8gYXV0b21hdGljYWxseSBidWlsZCBhIGRpc3RyaWJ1dGlvbiB0
cmVlIGZvciB0cmFuc3BvcnRpbmcgbXVsdGljYXN0IHRyYWZmaWMgYW5kIHByb3ZpZGVzIGEgbWV0
aG9kIG9mIHBydW5pbmcgdGhhdCB0cmVlIGZvciBpbXByb3ZlZCBlZmZpY2llbmN5Lg0KDQogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBh
IGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUg
aHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3Jn
Lg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From nobody Tue Oct 28 12:46:23 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B181C1ACD15; Tue, 28 Oct 2014 12:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.231
X-Spam-Level: 
X-Spam-Status: No, score=-1.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAi2iNnTv83o; Tue, 28 Oct 2014 12:46:18 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 102D81ACD04; Tue, 28 Oct 2014 12:46:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s9SJjuj4031557; Tue, 28 Oct 2014 19:45:56 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s9SJjuj4031557
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1414525556; bh=E4WStCiA8bKeYuGZOU8JfD2/qjI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=bxZteXgXnwDLVnGhyXqsCoLd4Ixqt5IIlxx14DYKB5ZxSUP8Xe3fC2C52x9qJphIZ +tnO4ADM9rLePEGTD9LbtXa0irk1N/a9/wHbX/UQD7gFuyWM+PC3jnMkfGhnL+AnjA pPQBdvhCp1Ov+ZtjUvUKzsTBHzivF4nzcN++vAts=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q9RJju07631119375H ret-id none; Tue, 28 Oct 2014 19:45:56 +0000
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s9SJik0r023263 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Oct 2014 19:44:47 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_A299BC16-851D-4B16-8D3E-E5873F004D4E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com>
Date: Tue, 28 Oct 2014 19:44:45 +0000
Message-ID: <EMEW3|17ee7d75db17a3a1b8e43f85ebccb07bq9RJju03tjc|ecs.soton.ac.uk|5C2EFB4E-925B-4252-BE58-894F9C061EA7@ecs.soton.ac.uk>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <5C2EFB4E-925B-4252-BE58-894F9C061EA7@ecs.soton.ac.uk>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q9RJju076311193700; tid=q9RJju07631119375H; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s9SJjuj4031557
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/VuZ0Qi1b9xDPKGVYA4iRCyrULts
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 19:46:20 -0000

--Apple-Mail=_A299BC16-851D-4B16-8D3E-E5873F004D4E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On 22 Oct 2014, at 21:16, Fred Baker (fred) <fred@cisco.com> wrote:

> On Oct 22, 2014, at 12:06 PM, David Lamparter <equinox@diac24.net> =
wrote:
>=20
>> On Mon, Oct 20, 2014 at 10:40:33PM +0200, David Lamparter wrote:
>>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-quali=
fiers/?include_text=3D1
>>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?in=
clude_text=3D1
>=20
> Speaking strictly for myself, I=92m not sure why homenet is relevant. =
The technology is related to networks that have different routing depend =
on on one=92s use case. A class of solutions for it has been called the =
=93fish=94 problem, and built using multi-topology routing. In homenet, =
it=92s called SADR, and is primarily about egress routing (routing to an =
egress to an upstream ISP that gave you a PA prefix). While one doesn=92t =
really want to confuse theory with practice, in theory it could be used =
between points of a network, to prevent folks using one set of prefixes =
to talk with another set, or to force routing of some sessions in some =
ways.
>=20
> Personally, those are a class of problems I associate with campus =
networks more than residential networks.

I suspect most campus networks will have a single /48 from their NREN, =
or a /48 PI. I=92m not aware of any campuses in the UK which are =
multi-homed with dual /48, though I understand some Internet2 campuses =
may be.=20

(As an aside we=92ve just run out of our v4 /16=85)

Homenet has =91designed in=92 future multihoming, which is rare today. =
In the homenet case the multihoming may presumably be more commonly for =
different services to the home?

Tim


--Apple-Mail=_A299BC16-851D-4B16-8D3E-E5873F004D4E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUT/ItAAoJEFoq8u2GfpfeP+8H/RaTDY7Oa7ws9pFVc7XpHMJw
R1mHrNIZ8+hZRhLxEbz5O/Ovm9dKhcE4QwBERZ7RHzPYwZPGdv3gqi5cDU7+m6XJ
F0MYyZddVT+KvZ2Lkt2b9FTPw2lVr0jcdqgkZS/9gHtyVJR78n2lSKcmel0h0qIT
DrZ8hY1DQr8xMdsxORC9FyqG1lfT9QoAWEOTDuV6fNCP+Mm1AigEnyJpaapu6eDm
paJp0HmRceDzB6inerQ91XQuyMGPeVEZA3PhWC9BMYKjt2+8LzYTnCrsg9XqkpAx
0QtW+dz+n+TrNwaIm7sPz+IybV7bOKuOSg/81lxZiMcpsQNAAXFj7rqokDMmJNY=
=QDRq
-----END PGP SIGNATURE-----

--Apple-Mail=_A299BC16-851D-4B16-8D3E-E5873F004D4E--


From nobody Tue Oct 28 23:00:04 2014
Return-Path: <equinox@diac24.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9439F1A033B for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 22:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001] autolearn=ham
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 saynLryhA2kn for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 22:59:57 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a02:238:f02a:8e2f:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E254D1A0242 for <rtgwg@ietf.org>; Tue, 28 Oct 2014 22:59:56 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.84) (envelope-from <equinox@diac24.net>) id 1XjMIK-0002PK-Jo; Wed, 29 Oct 2014 06:59:49 +0100
Date: Wed, 29 Oct 2014 06:59:44 +0100
From: David Lamparter <equinox@diac24.net>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141029055944.GE5186@eidolon>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <D0705F68.72BCB%aretana@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D0705F68.72BCB%aretana@cisco.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/FMSoAfO0atEi0gRs4n27TtftxS0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 05:59:59 -0000

On Fri, Oct 24, 2014 at 11:56:59PM +0000, Alvaro Retana (aretana) wrote:
> On 10/20/14, 4:40 PM, "David Lamparter" <equinox@diac24.net> wrote:
> 
> >Last but not least, I'd like to request a slot at the IETF 91 rtgwg
> >meeting to present these drafts.
> 
> David:
> 
> How much time do you want?

Hm.  5 min presentation + 5 min feedback?

(Total, presenting 2Â½ drafts, Â½ being Fred's original usecase one which
I'd just mention as reference document.  I don't foresee significant
changes coming to the use-case doc, no idea what how to proceed with it
to be honest?)

The goal I have in mind for IETF91 is to get an ACK / NAK from the room
on whether to proceed, so I guess the feedback part is most important.
To be entirely honest I have no clue how much feedback there'll be...

(Apologies for the delay, I've been out sick over the weekend)


-David


From nobody Tue Oct 28 23:28:45 2014
Return-Path: <equinox@diac24.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 272A61A0673; Tue, 28 Oct 2014 23:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 uuXQPWoPtQUw; Tue, 28 Oct 2014 23:28:41 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a02:238:f02a:8e2f:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BD81A0451; Tue, 28 Oct 2014 23:28:41 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.84) (envelope-from <equinox@diac24.net>) id 1XjMkH-0002aQ-1k; Wed, 29 Oct 2014 07:28:38 +0100
Date: Wed, 29 Oct 2014 07:28:37 +0100
From: David Lamparter <equinox@diac24.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141029062837.GH5186@eidolon>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <544FF3F2.3050206@gmail.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/BkojPFLjVKWeAX_vbQpx8586OH4
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 06:28:43 -0000

On Wed, Oct 29, 2014 at 08:52:18AM +1300, Brian E Carpenter wrote:
> On 29/10/2014 02:06, Ole Troan wrote:
> > Fred,
> > 
> >>>> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-qualifiers/?include_text=1
> >>>> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?include_text=1
> >> Speaking strictly for myself, Iâ€™m not sure why homenet is relevant. The technology is related to networks that have different routing depend on on oneâ€™s use case. A class of solutions for it has been called the â€œfishâ€� problem, and built using multi-topology routing. In homenet, itâ€™s called SADR, and is primarily about egress routing (routing to an egress to an upstream ISP that gave you a PA prefix). While one doesnâ€™t really want to confuse theory with practice, in theory it could be used between points of a network, to prevent folks using one set of prefixes to talk with another set, or to force routing of some sessions in some ways.
> >>
> >> Personally, those are a class of problems I associate with campus networks more than residential networks.
> > 
> > why homenet is relevant?
> > isn't multi-prefix multi-homing one of the most obvious use cases for source address dependent routing? that's not restricted with homenets, but also any small network. I'm assuming large networks will continue with PI addresses and BGP based multihoming.
> 
> If you mean by "large" the few ten thousand largest networks in the
> world, that will not cause significant BGP4 bloat by having PI, then
> yes, I fully agree. Any medium to small network should expect to have
> multiple prefixes in the long run (we are not talking about today, but
> a time when all we old folks who remember the IPv4 world have retired
> and gone fishing).

What I'm personally wondering most in this regard is: to what extent
will larger networks deploy multiple prefixes to the hosts?

I can certainly see it in small to medium businesses that maybe just got
their second uplink at their headquarters and opened 3 shops or
whatever.  But at some point I'd guess policy/enforcement replaces
multiprefix deployments, as Gert wrote in his mail.  Then again, some
shiny new things like MPTCP would benefit from multiprefix deployments,
which might be an argument for some medium-sized users to deploy this?


FWIW, I understand Fred's question for the relevance of homenet as
asking whether these drafts should explicitly target homenet or not, and
I agree that they shouldn't.  Even if 90% of SADR use-cases end up to be
"bread and butter" homenets, the remaining 10% are valid too.


-David


From nobody Tue Oct 28 23:50:36 2014
Return-Path: <fred@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4164D1A1B17; Tue, 28 Oct 2014 23:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 Y-gINgaMGAv9; Tue, 28 Oct 2014 23:50:19 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13FE01A1A1C; Tue, 28 Oct 2014 23:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1337; q=dns/txt; s=iport; t=1414565419; x=1415775019; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xwvEhg6DBrxvy6NV8EfiKONfdPSNwn6H7VcSbsbu/ZI=; b=OvRpdmfwqkWwOO2zRYjxXetz2xWMenIhPhf7JZv7sbUZAb/BARS6ohTL VTt1hA2fXVcdiPn2+74bTohNSu2Hn78eCQ0bPu+EKgqLSx4IUrAFhA3Mm FmEeGV6cXjhmB3xGkGGcBOtonFehdPLw+jJP6srltQleP/SdrW51YjCd5 c=;
X-Files: signature.asc : 195
X-IronPort-AV: E=Sophos;i="5.04,808,1406592000";  d="asc'?scan'208";a="91287274"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-8.cisco.com with ESMTP; 29 Oct 2014 06:50:17 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s9T6oHHN031698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Oct 2014 06:50:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.248]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 01:50:17 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Thread-Topic: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Thread-Index: AQHP7KYr8Fy7zf5Z70yFtC9ToRE4KA==
Date: Wed, 29 Oct 2014 06:50:17 +0000
Message-ID: <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon>
In-Reply-To: <20141029062837.GH5186@eidolon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: multipart/signed; boundary="Apple-Mail=_71B80352-0042-4026-A97C-A58CF7EF403E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/KauWZEOstMekKWawXHaeQ_rcz9c
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 06:50:24 -0000

--Apple-Mail=_71B80352-0042-4026-A97C-A58CF7EF403E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 28, 2014, at 11:28 PM, David Lamparter <equinox@diac24.net> =
wrote:

> What I'm personally wondering most in this regard is: to what extent
> will larger networks deploy multiple prefixes to the hosts?

Well, define =93larger=94. Any network that gets a PI prefix is unlikely =
to deploy multiple prefixes. The question is at what size network is =
makes sense to obtain an AS number and a PI prefix, and use BGP to talk =
with one=92s upstream. Wherever that boundary is, below that networks =
will use PA prefixes. The question then becomes: will they multi home?

And I think the answer today is that we don=92t know the answer.

--Apple-Mail=_71B80352-0042-4026-A97C-A58CF7EF403E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUUI4ibjEdbHIsm0MRAiXHAKDNLmSA5OJdR0hascpe6gM2EgNufQCgkfWX
Zk3WB/wxsiNP1qmSRE9xIOg=
=7ndN
-----END PGP SIGNATURE-----

--Apple-Mail=_71B80352-0042-4026-A97C-A58CF7EF403E--


From nobody Wed Oct 29 07:14:08 2014
Return-Path: <v6ops@globis.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7EF31A0078; Wed, 29 Oct 2014 05:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RaBZD6tjAfig; Wed, 29 Oct 2014 05:05:47 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D16471A0076; Wed, 29 Oct 2014 05:05:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 6B1E7871612; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYhcOzxypzPf; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 3F00D871611; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Message-ID: <5450D7ED.9010806@globis.net>
Date: Wed, 29 Oct 2014 13:05:01 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon> <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com>
In-Reply-To: <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Bpyt4lhQ6h6FQGvsTLwsnmxcgC0
X-Mailman-Approved-At: Wed, 29 Oct 2014 07:13:56 -0700
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 12:05:48 -0000

Fred Baker (fred) wrote:
> On Oct 28, 2014, at 11:28 PM, David Lamparter<equinox@diac24.net>  wrote:
>
>> What I'm personally wondering most in this regard is: to what extent
>> will larger networks deploy multiple prefixes to the hosts?
>
> Well, define “larger”. Any network that gets a PI prefix is unlikely to deploy multiple prefixes. The question is at what size network is makes sense to obtain an AS number and a PI prefix, and use BGP to talk with one’s upstream.
I don't agree with this statement for the following reasons.

Availability: There are many enterprises that have very numerous 
far-flung sales-office type locations which do not host any critical 
data or applications, but which could benefit from higher availability 
than that provided by a single ISP provider (some of which are currently 
served by a specialised box offering a Very Small Office Service running 
dual IPSec tunnels to a central site, which then performs the break out 
to the corporate intranet/Internet)

Latency: There are many sites which could benefit from local Internet 
breakout to regional cloud services, where you don't want to suffer the 
latency associated with a back haul from an office in Australia to a 
regional hub in Hong Kong, or even East coast US to West coast US and 
back. You'd still also want some back up via the central breakout if the 
local breakout failed.

Cost: There are cost savings to be made in many countries where private 
network services are still many orders of magnitude more expensive than 
plain old Internet. So Internet offload for non-mission-critical traffic 
can be very attractive. If you could achieve this via direct host-server 
connections using address selection rules or multipath TCP; rather than 
via PBR, GRE tunnels + NAT, that would be a lot simpler.

>   Wherever that boundary is, below that networks will use PA prefixes. The question then becomes: will they multi home?
>
> And I think the answer today is that we don’t know the answer.
This I agree with.


-- 
Regards,
RayH


From nobody Wed Oct 29 07:14:10 2014
Return-Path: <ot@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5625A1A6FAA; Tue, 28 Oct 2014 06:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 sl9nvQMLG3Ze; Tue, 28 Oct 2014 06:06:35 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D78C1A6FE7; Tue, 28 Oct 2014 06:06:35 -0700 (PDT)
Received: from [192.168.10.30] (cm-84.215.22.20.getinternet.no [84.215.22.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 6087B628B; Tue, 28 Oct 2014 06:06:33 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
From: Ole Troan <ot@cisco.com>
In-Reply-To: <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com>
Date: Tue, 28 Oct 2014 14:06:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/7gEL57aybrr_GCnDCPt7G5dqpIc
X-Mailman-Approved-At: Wed, 29 Oct 2014 07:14:02 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 13:06:39 -0000

Fred,

>>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-quali=
fiers/?include_text=3D1
>>> =
https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?in=
clude_text=3D1
>=20
> Speaking strictly for myself, I=92m not sure why homenet is relevant. =
The technology is related to networks that have different routing depend =
on on one=92s use case. A class of solutions for it has been called the =
=93fish=94 problem, and built using multi-topology routing. In homenet, =
it=92s called SADR, and is primarily about egress routing (routing to an =
egress to an upstream ISP that gave you a PA prefix). While one doesn=92t =
really want to confuse theory with practice, in theory it could be used =
between points of a network, to prevent folks using one set of prefixes =
to talk with another set, or to force routing of some sessions in some =
ways.
>=20
> Personally, those are a class of problems I associate with campus =
networks more than residential networks.

why homenet is relevant?
isn't multi-prefix multi-homing one of the most obvious use cases for =
source address dependent routing? that's not restricted with homenets, =
but also any small network. I'm assuming large networks will continue =
with PI addresses and BGP based multihoming.

cheers,
Ole=


From nobody Wed Oct 29 07:14:11 2014
Return-Path: <gert@Space.Net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108021A8789 for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 06:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 q4YP1pruUVIk for <rtgwg@ietfa.amsl.com>; Tue, 28 Oct 2014 06:18:58 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70E511A8776 for <rtgwg@ietf.org>; Tue, 28 Oct 2014 06:18:05 -0700 (PDT)
X-Original-To: rtgwg@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 7840E6035E for <rtgwg@ietf.org>; Tue, 28 Oct 2014 14:18:03 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 2D4D560102 for <rtgwg@ietf.org>; Tue, 28 Oct 2014 14:18:03 +0100 (CET)
Received: (qmail 23745 invoked by uid 1007); 28 Oct 2014 14:18:03 +0100
Date: Tue, 28 Oct 2014 14:18:03 +0100
From: Gert Doering <gert@space.net>
To: Ole Troan <ot@cisco.com>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141028131803.GN31092@Space.Net>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/E2bvDaoGUW0ekaxjunNpD8m4rhc
X-Mailman-Approved-At: Wed, 29 Oct 2014 07:13:58 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 13:19:00 -0000

Hi,

On Tue, Oct 28, 2014 at 02:06:26PM +0100, Ole Troan wrote:
> isn't multi-prefix multi-homing one of the most obvious use cases
> for source address dependent routing? that's not restricted with
> homenets, but also any small network. I'm assuming large networks
> will continue with PI addresses and BGP based multihoming.

I see the distinction somewhere in the "what defines policy in a network",
as in:

 - in a "big" company network, there usually is some sort of network access
   policy, which is defined and enforced by the network people - so you'll
   see BGP policies and PI, or in a "dual /48" style shop, I expect to see
   dual-NPT66-with-ULA devices where you can configure your policy ("surfing
   goes out via ISP A, mail goes out via ISP B") in the network device

 - in a homenet, small company ("barber shop") network, there is no "admin",
   and to try to enforce network policy ("surfing via cable, bittorrent via
   DSL") in the network device is futile, because "no admin".  So here you
   need SADR to empower the end device - and by that means, the user - to
   define policy.  Have the bittorrent client use the source address from
   the DSL ISP's /48, the web browser use the source address from the 
   Cable ISP, and things work the way the user wants it.

   ... and this is why I really really like dual-/48 multihoming for the
   "not really managed" SOHO case, as it puts policy decisions where they
   can be made (= user's device) - and of course, why dual-/48 is not going
   to fly for enterprise networks (= can't have the user decide that).


(In case this wasn't obvious, I'm agreeing with Ole here, I just try to
shed light from a slightly different angle on that.)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Wed Oct 29 07:14:13 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8DA1ACCEC; Tue, 28 Oct 2014 12:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 wn_M4E96z6y6; Tue, 28 Oct 2014 12:52:49 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A349A1ACD82; Tue, 28 Oct 2014 12:52:19 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kx10so1478772pab.6 for <multiple recipients>; Tue, 28 Oct 2014 12:52:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WG3YzXprql5Q4a8hW0BCIOtV3PiDF958hmSZoT+1af8=; b=sa+upQXhXbWzHDWBEeLNqy25sT/MIOYLa3egRNBkDCdsdgKH4lbsqKqKUtjQcXFunA jl3LSZ6Vpq9t0aD0brvPkq5Wy91GQtK/EuF9jvHd9SdLyYTItQ7ggJOvjUQ2URVAUn7X nU7/2ooqN9B6h2pF0rwCDDfVj/FxqgfZ1yUjrfYzreo1AxKM1HY6EjaaLQ15wFVCF+lk 8IupcRWYspkVg6vi3I9DIUKKHokR7MYcYupI8rz1GENge4EEnn+BPeDlF3gaCHfjwAGZ JQYqKoXjc0VbwpAN+FXw1DQPxuLdXj57MtL/1Nxiy7f7tikdh0VgoFdN59n4GMZmr1KY TR1Q==
X-Received: by 10.68.185.98 with SMTP id fb2mr3885558pbc.142.1414525939381; Tue, 28 Oct 2014 12:52:19 -0700 (PDT)
Received: from [192.168.178.23] (162.194.69.111.dynamic.snap.net.nz. [111.69.194.162]) by mx.google.com with ESMTPSA id zn11sm2396554pab.24.2014.10.28.12.52.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Oct 2014 12:52:18 -0700 (PDT)
Message-ID: <544FF3F2.3050206@gmail.com>
Date: Wed, 29 Oct 2014 08:52:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com>
In-Reply-To: <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/81yboyr5Qw2-3qlSxicdUAmTM-c
X-Mailman-Approved-At: Wed, 29 Oct 2014 07:14:02 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Oct 2014 19:52:52 -0000

On 29/10/2014 02:06, Ole Troan wrote:
> Fred,
>=20
>>>> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra=
-qualifiers/?include_text=3D1
>>>> https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routi=
ng/?include_text=3D1
>> Speaking strictly for myself, I=E2=80=99m not sure why homenet is rele=
vant. The technology is related to networks that have different routing d=
epend on on one=E2=80=99s use case. A class of solutions for it has been =
called the =E2=80=9Cfish=E2=80=9D problem, and built using multi-topology=
 routing. In homenet, it=E2=80=99s called SADR, and is primarily about eg=
ress routing (routing to an egress to an upstream ISP that gave you a PA =
prefix). While one doesn=E2=80=99t really want to confuse theory with pra=
ctice, in theory it could be used between points of a network, to prevent=
 folks using one set of prefixes to talk with another set, or to force ro=
uting of some sessions in some ways.
>>
>> Personally, those are a class of problems I associate with campus netw=
orks more than residential networks.
>=20
> why homenet is relevant?
> isn't multi-prefix multi-homing one of the most obvious use cases for s=
ource address dependent routing? that's not restricted with homenets, but=
 also any small network. I'm assuming large networks will continue with P=
I addresses and BGP based multihoming.

If you mean by "large" the few ten thousand largest networks in the
world, that will not cause significant BGP4 bloat by having PI, then
yes, I fully agree. Any medium to small network should expect to have
multiple prefixes in the long run (we are not talking about today, but
a time when all we old folks who remember the IPv4 world have retired
and gone fishing).

   Brian


From nobody Wed Oct 29 08:14:11 2014
Return-Path: <gettysjim@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0711A01C6; Wed, 29 Oct 2014 08:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4KSESS9uG37m; Wed, 29 Oct 2014 08:13:39 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18FD01A0171; Wed, 29 Oct 2014 08:13:39 -0700 (PDT)
Received: by mail-oi0-f49.google.com with SMTP id u20so2418589oif.22 for <multiple recipients>; Wed, 29 Oct 2014 08:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=f/WZlpDJU9UsoaWtJV2vPS4PGrqcO+8iTk3w5WyTYjI=; b=e2vZUKzP31vYR3BBuo8o3V9G1DlGq7P7ClXZyYs3WAkhbM/qlYyA9XBRaEMsDWBhDX D86JZbW5s9Adu+L77YU2k0WiGfl/XGbqpXuHWZor92nh8Ve8HsBwS2CJeto+yyHudgGQ OjypYvNKz48NISc+ox5qBKfLh1PVRSQguKo0/E2O0NiSlUAavW6NkMOng/BYcavDFZKd SBwtEKF8TkII3C2FLc9bFcbk/MiJgCnqT18DWRl8nSHSX5xhCeUNNQyuQLpD5nspopLu 94uAyrR8ew8r70wtavnKY67MzOL5MVswqeoFPCC5IgUc6XOXoeBPfhjSTlqxc4fiOqYg DmVg==
MIME-Version: 1.0
X-Received: by 10.60.157.100 with SMTP id wl4mr9228686oeb.37.1414595617464; Wed, 29 Oct 2014 08:13:37 -0700 (PDT)
Sender: gettysjim@gmail.com
Received: by 10.76.4.203 with HTTP; Wed, 29 Oct 2014 08:13:37 -0700 (PDT)
In-Reply-To: <5450D7ED.9010806@globis.net>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon> <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com> <5450D7ED.9010806@globis.net>
Date: Wed, 29 Oct 2014 11:13:37 -0400
X-Google-Sender-Auth: -paScE3WgopxfKj55TksJCFvEao
Message-ID: <CAGhGL2DLLMghFCdXtbvRy1O7Ab8QPcEuPhZczOa8Mi9pmQnwVg@mail.gmail.com>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
From: Jim Gettys <jg@freedesktop.org>
To: Ray Hunter <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=089e01182fd047a90f05069135ba
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/U2a07Gdw0qmd_nAK-rkC4yU9Hbg
Cc: Ole Troan <ot@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 15:13:44 -0000

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

On Wed, Oct 29, 2014 at 8:05 AM, Ray Hunter <v6ops@globis.net> wrote:

>
>
> Fred Baker (fred) wrote:
>
>> On Oct 28, 2014, at 11:28 PM, David Lamparter<equinox@diac24.net>  wrote=
:
>>
>>  What I'm personally wondering most in this regard is: to what extent
>>> will larger networks deploy multiple prefixes to the hosts?
>>>
>>
>> Well, define =E2=80=9Clarger=E2=80=9D. Any network that gets a PI prefix=
 is unlikely to
>> deploy multiple prefixes. The question is at what size network is makes
>> sense to obtain an AS number and a PI prefix, and use BGP to talk with
>> one=E2=80=99s upstream.
>>
> I don't agree with this statement for the following reasons.
>
> Availability: There are many enterprises that have very numerous far-flun=
g
> sales-office type locations which do not host any critical data or
> applications, but which could benefit from higher availability than that
> provided by a single ISP provider (some of which are currently served by =
a
> specialised box offering a Very Small Office Service running dual IPSec
> tunnels to a central site, which then performs the break out to the
> corporate intranet/Internet)
>

=E2=80=8B
=E2=80=8B
=E2=80=8BAnd we are now deploying home networks that are being used for hom=
e health
medical monitoring; having full fail-over to another ISP is in the process
of becoming a "life" issue=E2=80=8B.
=E2=80=8B
=E2=80=8B


>
> Latency: There are many sites which could benefit from local Internet
> breakout to regional cloud services, where you don't want to suffer the
> latency associated with a back haul from an office in Australia to a
> regional hub in Hong Kong, or even East coast US to West coast US and bac=
k.
> You'd still also want some back up via the central breakout if the local
> breakout failed.
>
> Cost: There are cost savings to be made in many countries where private
> network services are still many orders of magnitude more expensive than
> plain old Internet. So Internet offload for non-mission-critical traffic
> can be very attractive. If you could achieve this via direct host-server
> connections using address selection rules or multipath TCP; rather than v=
ia
> PBR, GRE tunnels + NAT, that would be a lot simpler.

=E2=80=8B

>
>
>    Wherever that boundary is, below that networks will use PA prefixes.
>> The question then becomes: will they multi home?
>>
>> And I think the answer today is that we don=E2=80=99t know the answer.
>>
> This I agree with.


=E2=80=8BDitto.  Though I have a personal opinion that they will... How els=
e can
you be able to test that things are actually going to "work" in the face of
loss of one ISP? Anything not being tested on an ongoing basis is unlikely
to work in the case of failure.  If availability really matters, you care..=
.

Jim

=E2=80=8B


>
>
>
> --
> Regards,
> RayH
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Oc=
t 29, 2014 at 8:05 AM, Ray Hunter <span dir=3D"ltr">&lt;<a href=3D"mailto:v=
6ops@globis.net" target=3D"_blank">v6ops@globis.net</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid=
;padding-left:1ex"><span class=3D""><br>
<br>
Fred Baker (fred) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
On Oct 28, 2014, at 11:28 PM, David Lamparter&lt;<a href=3D"mailto:equinox@=
diac24.net" target=3D"_blank">equinox@diac24.net</a>&gt;=C2=A0 wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
What I&#39;m personally wondering most in this regard is: to what extent<br=
>
will larger networks deploy multiple prefixes to the hosts?<br>
</blockquote>
<br>
Well, define =E2=80=9Clarger=E2=80=9D. Any network that gets a PI prefix is=
 unlikely to deploy multiple prefixes. The question is at what size network=
 is makes sense to obtain an AS number and a PI prefix, and use BGP to talk=
 with one=E2=80=99s upstream.<br>
</blockquote></span>
I don&#39;t agree with this statement for the following reasons.<br>
<br>
Availability: There are many enterprises that have very numerous far-flung =
sales-office type locations which do not host any critical data or applicat=
ions, but which could benefit from higher availability than that provided b=
y a single ISP provider (some of which are currently served by a specialise=
d box offering a Very Small Office Service running dual IPSec tunnels to a =
central site, which then performs the break out to the corporate intranet/I=
nternet)<br></blockquote><div><br></div><div><div class=3D"gmail_default" s=
tyle=3D"font-size:small;display:inline">=E2=80=8B</div>=E2=80=8B</div><div>=
<div class=3D"gmail_default" style=3D"font-size:small;display:inline"><div =
class=3D"gmail_default" style=3D"display:inline">=E2=80=8BAnd we are now de=
ploying home networks that are being used for home health medical monitorin=
g; having full fail-over to another ISP is in the process of becoming a &qu=
ot;life&quot; issue=E2=80=8B.=C2=A0</div></div></div><div><div class=3D"gma=
il_default" style=3D"font-size:small;display:inline"><div class=3D"gmail_de=
fault" style=3D"display:inline">=E2=80=8B</div>=E2=80=8B</div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa=
dding-left:1ex">
<br>
Latency: There are many sites which could benefit from local Internet break=
out to regional cloud services, where you don&#39;t want to suffer the late=
ncy associated with a back haul from an office in Australia to a regional h=
ub in Hong Kong, or even East coast US to West coast US and back. You&#39;d=
 still also want some back up via the central breakout if the local breakou=
t failed.<br>
<br>
Cost: There are cost savings to be made in many countries where private net=
work services are still many orders of magnitude more expensive than plain =
old Internet. So Internet offload for non-mission-critical traffic can be v=
ery attractive. If you could achieve this via direct host-server connection=
s using address selection rules or multipath TCP; rather than via PBR, GRE =
tunnels + NAT, that would be a lot simpler.</blockquote><div><div class=3D"=
gmail_default" style=3D"font-size:small">=E2=80=8B</div></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1=
ex"><span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
=C2=A0 Wherever that boundary is, below that networks will use PA prefixes.=
 The question then becomes: will they multi home?<br>
<br>
And I think the answer today is that we don=E2=80=99t know the answer.<br>
</blockquote></span>
This I agree with.</blockquote><div><br></div><div><div class=3D"gmail_defa=
ult" style=3D"font-size:small;display:inline">=E2=80=8BDitto.=C2=A0 Though =
I have a personal opinion that they will... How else can you be able to tes=
t that things are actually going to &quot;work&quot; in the face of loss of=
 one ISP? Anything not being tested on an ongoing basis is unlikely to work=
 in the case of failure.=C2=A0 If availability really matters, you care...<=
/div></div><div><div class=3D"gmail_default" style=3D"font-size:small;displ=
ay:inline"><br></div></div><div><div class=3D"gmail_default" style=3D"font-=
size:small;display:inline">Jim</div></div><div><div class=3D"gmail_default"=
 style=3D"font-size:small;display:inline"><br></div></div><div><div class=
=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8B</div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex"><span class=3D""><font color=3D"#888888"><br>
<br>
<br>
-- <br>
Regards,<br>
RayH</font></span><div class=3D""><div class=3D"h5"><br>
<br>
______________________________<u></u>_________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/<u></u>listinfo/homenet</a><br>
</div></div></blockquote></div><br></div></div>

--089e01182fd047a90f05069135ba--


From nobody Wed Oct 29 09:09:30 2014
Return-Path: <fred@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1EF21A1AEB; Wed, 29 Oct 2014 09:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 fV0VKRLMommJ; Wed, 29 Oct 2014 09:09:17 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEAF51A1A4E; Wed, 29 Oct 2014 09:09:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5723; q=dns/txt; s=iport; t=1414598957; x=1415808557; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=2QWzecaPC0eydHgZPn18j4Gr7oDQQYS737TOKLAGrK0=; b=kz3HBi9szpE+yv8QcBxK3qV+dh4PfmLF+cPgE4ruRv77mcWm+wBthS9m Rp6pU7hoi/sgeE7uwGnZSfc4xp3d7rComa8JBhluxNZSTQAJESUw5EuFZ i2EThMeH8fiU847tP9gKtkmR+OBClVKJanb19gpbUzv/g7GW4J3mgR5SW Q=;
X-Files: signature.asc : 195
X-IronPort-AV: E=Sophos;i="5.04,810,1406592000";  d="asc'?scan'208";a="367613256"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 29 Oct 2014 16:09:15 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s9TG9F93026139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Oct 2014 16:09:15 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.248]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 11:09:15 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Ray Hunter <v6ops@globis.net>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Thread-Topic: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Thread-Index: AQHP7KYr8Fy7zf5Z70yFtC9ToRE4KA==
Date: Wed, 29 Oct 2014 16:09:15 +0000
Message-ID: <C9754B86-0A54-4FA5-91B5-4D4339E8D9C8@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon> <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com> <5450D7ED.9010806@globis.net>
In-Reply-To: <5450D7ED.9010806@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: multipart/signed; boundary="Apple-Mail=_6D616973-B317-4DAA-9C1D-B9051EFAA046"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/4YwiGgG_AhfpmXJapMtnWGDDXFA
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 16:09:20 -0000

--Apple-Mail=_6D616973-B317-4DAA-9C1D-B9051EFAA046
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 29, 2014, at 5:05 AM, Ray Hunter <v6ops@globis.net> wrote:

>=20
>=20
> Fred Baker (fred) wrote:
>> On Oct 28, 2014, at 11:28 PM, David Lamparter<equinox@diac24.net>  =
wrote:
>>=20
>>> What I'm personally wondering most in this regard is: to what extent
>>> will larger networks deploy multiple prefixes to the hosts?
>>=20
>> Well, define =93larger=94. Any network that gets a PI prefix is =
unlikely to deploy multiple prefixes. The question is at what size =
network is makes sense to obtain an AS number and a PI prefix, and use =
BGP to talk with one=92s upstream.
>=20
> I don't agree with this statement for the following reasons.
>=20
> Availability: There are many enterprises that have very numerous =
far-flung sales-office type locations which do not host any critical =
data or applications, but which could benefit from higher availability =
than that provided by a single ISP provider (some of which are currently =
served by a specialised box offering a Very Small Office Service running =
dual IPSec tunnels to a central site, which then performs the break out =
to the corporate intranet/Internet)
>=20
> Latency: There are many sites which could benefit from local Internet =
breakout to regional cloud services, where you don't want to suffer the =
latency associated with a back haul from an office in Australia to a =
regional hub in Hong Kong, or even East coast US to West coast US and =
back. You'd still also want some back up via the central breakout if the =
local breakout failed.
>=20
> Cost: There are cost savings to be made in many countries where =
private network services are still many orders of magnitude more =
expensive than plain old Internet. So Internet offload for =
non-mission-critical traffic can be very attractive. If you could =
achieve this via direct host-server connections using address selection =
rules or multipath TCP; rather than via PBR, GRE tunnels + NAT, that =
would be a lot simpler.

I have a hunch we=92re talking past each other. We would agree, but =
we=92re discussing different cases. I was discussing a case in which a =
company operates a single addressing plan. I think you=92re discussing a =
company that operates multiple addressing plans, one for each of several =
locations.

Cisco might be an example of a =93larger=94 company. We have an IPv6 =
/32, more locations than you can shake a stick at, and maybe 20 DMZs, =
places where our network interconnects with the Internet. I don=92t know =
exactly what we advertise or where, but I could imagine that a few of =
our DMZs advertise the /32 and each of our DMZs advertises a /40, or =
something along that line. For us, PI is =93duh, obvious=94, and the =
only case in which we might - *might* - have a second prefix would be a =
ULA in a lab.

I suspect the company you are discussing might have a number of small =
offices in as many cities, and as many PA prefixes as it takes. The =
company might also have a PI prefix, but I would be surprised if it used =
the PI prefix in all of its little offices; if it did, it would =
essentially use it for internal traffic, and have some sort of VPN =
connecting the offices on which it was used. It would, however, use the =
PA prefixes from the offices when they need to talk outside the house. =
If it is using the PI prefix plus a PA prefix in any given office, it =
would depend on RFC 6724=92s Rule 8 (longest match) to prefer a PI =
address when talking to another address within the prefix, and a =
temporary address from PA space otherwise.

In any event, in the context of my comment above, I am thinking of the =
many small offices as separate networks. They don=92t justify their own =
PI spaces; the PI in context acts more like PA from the central =
corporation than PI in the traditional sense of the term. They might =
well get PA from one or more ISPs, and they might have something akin to =
PA from their central office or whatever.

Coming back to the question - =93would they put multiple subnet prefixes =
on any given LAN=94 - the question really comes back to their =
requirements and stomach for complexity. If they require multihoming, =
such as Jim suggests, I would hope they would do that. Among my =93NAT =
=3D=3D Security=94 customers and SEs, getting them there requires their =
network to work well (egress routing being one of many important parts =
of that), and a good security solution that doesn=92t involve NAT. Until =
they have one AND they are convinced, they tell us that the lack of a =
NAT solution is a reason to delay deployment. I don=92t think that last =
is about the number of prefixes around; it=92s about security policy and =
mindset.

>>  Wherever that boundary is, below that networks will use PA prefixes. =
The question then becomes: will they multi home?
>>=20
>> And I think the answer today is that we don=92t know the answer.
>=20
> This I agree with.
>=20
>=20
> --=20
> Regards,
> RayH
>=20


--Apple-Mail=_6D616973-B317-4DAA-9C1D-B9051EFAA046
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUUREhbjEdbHIsm0MRAjvPAKDV09l2avuGVLDfwVF56b1rxWovfwCfZGGH
PXoegO/XxUeMdkj69FwYTDc=
=Tn9I
-----END PGP SIGNATURE-----

--Apple-Mail=_6D616973-B317-4DAA-9C1D-B9051EFAA046--


From nobody Wed Oct 29 13:01:00 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566821A87AC; Wed, 29 Oct 2014 11:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 VcUACjvWqkD4; Wed, 29 Oct 2014 11:24:12 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40C721A879D; Wed, 29 Oct 2014 11:24:05 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 19429203AA; Wed, 29 Oct 2014 14:25:23 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1077263A84; Wed, 29 Oct 2014 14:24:03 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EE45763A80; Wed, 29 Oct 2014 14:24:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
In-Reply-To: <EMEW3|17ee7d75db17a3a1b8e43f85ebccb07bq9RJju03tjc|ecs.soton.ac.uk|5C2EFB4E-925B-4252-BE58-894F9C061EA7@ecs.soton.ac.uk>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <5C2EFB4E-925B-4252-BE58-894F9C061EA7@ecs.soton.ac.uk> <EMEW3|17ee7d75db17a3a1b8e43f85ebccb07bq9RJju03tjc|ecs.soton.ac.uk|5C2EFB4E-925B-4252-BE58-894F9C061EA7@ecs.soton.ac.uk>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 Oct 2014 14:24:03 -0400
Message-ID: <28735.1414607043@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/HP8mbbveD2LVNvIo4HLep4N4B4c
X-Mailman-Approved-At: Wed, 29 Oct 2014 13:00:56 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 18:24:13 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Tim Chown <tjc@ecs.soton.ac.uk> wrote:
    > Homenet has =E2=80=98designed in=E2=80=99 future multihoming, which i=
s rare today. In
    > the homenet case the multihoming may presumably be more commonly for
    > different services to the home?

It's true that real multihoming (in the home...) is rare.

There are a multitude of off-the-shelf SOHO routers which support multiple
uplinks via NAPT.  I have setup this kind of thing up for a few dozen
friends' companies over the years... usually via a cablemodel + DSL (from
different suppliers) because we are protecting from a combination of
backhaul events and "customer service".

All of the downtime I've seen in the past ten years in my home office has
been due to "initiatives" from "customer service".

So I am very happy with the features that we have built-in, and I think with
the growth of 3G we will see additional mechanisms.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVFEwwYCLcPvd0N1lAQIIKwf+LnZM+0xNjgNjM0D81a6fQOgFa6n9ngC0
dULmlZsGioBJCCgRaedBuk2U3icRSY7YSBr4+dGOqZLLr1QRoIDf5kb2VIs11Mww
UBHjJw33l7Zlpw53zJodzDnUvR9zeoXgwgtmeV4imIwVXJ2TqBSPLUsSlqfQYiTh
4eo1Vxjr1lPstYhr5ZsvAZqDeQtNlyoA4B+H2Y1rkOH60i6NIY8A/zxeFg3BrLU6
Aj2rn+ycBY6c26nya77unoFBHY2hUySbP091eZp7TjgYkBjxNS/ndHPECwyCN/b+
IiKtjf88wlBaxbTvZ4CKNwNnOxH631N/meTs3YY5ZD7AqSkzQFU4OA==
=Vl4a
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Oct 29 17:39:45 2014
Return-Path: <equinox@diac24.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF891ACE84; Wed, 29 Oct 2014 17:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 t7mUoPCyNoKy; Wed, 29 Oct 2014 17:39:40 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a02:238:f02a:8e2f:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1784A1ACE81; Wed, 29 Oct 2014 17:39:39 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.84) (envelope-from <equinox@diac24.net>) id 1Xjdm1-000DwA-SK; Thu, 30 Oct 2014 01:39:34 +0100
Date: Thu, 30 Oct 2014 01:39:33 +0100
From: David Lamparter <equinox@diac24.net>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Message-ID: <20141030003933.GS5186@eidolon>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon> <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com> <5450D7ED.9010806@globis.net> <C9754B86-0A54-4FA5-91B5-4D4339E8D9C8@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C9754B86-0A54-4FA5-91B5-4D4339E8D9C8@cisco.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/_Ua_JXHTHbdL0yOjcKxbft7NPkQ
Cc: Ole Troan <ot@cisco.com>, Ray Hunter <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 00:39:42 -0000

[plucking a paragraph from the middle]
On Wed, Oct 29, 2014 at 04:09:15PM +0000, Fred Baker (fred) wrote:
> I suspect the company you are discussing might have a number of small
> offices in as many cities, and as many PA prefixes as it takes. The
> company might also have a PI prefix, but I would be surprised if it
> used the PI prefix in all of its little offices; if it did, it would
> essentially use it for internal traffic, and have some sort of VPN
> connecting the offices on which it was used. It would, however, use
> the PA prefixes from the offices when they need to talk outside the
> house. If it is using the PI prefix plus a PA prefix in any given
> office, it would depend on RFC 6724â€™s Rule 8 (longest match) to prefer
> a PI address when talking to another address within the prefix, and a
> temporary address from PA space otherwise.

If there is an overlap of a company-wide numbering plan with local
connectivity, that might actually be use-case for a SADR route whose
destination isn't ::/0.  Though you could always do that with a simple
destination route for the company-wide prefix, what you can now do is
signal the correlations between routes.  (Except we don't have a
protocol to communicate this to the host yet.)

I'm imagining a route table like this:
(:cccc: being the company-wide PI)

::/0 from 2001:db8:1::/48 via PA-provider-1
::/0 from 2001:db8:2::/48 via PA-provider-2
::/0 from 2001:db8:cccc::/48 unreachable
2001:db8:cccc::/48 from 2001:db8:cccc::/48 via IPsec-gateway
2001:db8:cccc::/48 from ::/0 unreachable

Where the last route would prevent accidental leaking of packets onto
the internet in case the IPsec gateway malfunctions.  (The 3rd route is
redundant if there's no "::/0 from ::/0")

But - apart from ease of use for multiple prefixes, this can be done
without SADR just fine, the only advantage is that there's full
information regarding which source addresses work with which
destinations.  If we get that to hosts, and into their source address
selection, then we won something.

(And this is really the same as homenet walled-garden scenarios, where
an ISP uses a separate prefix for some [IPTV, whatever] service and
expects clients to use a distinct source prefix to get to that service.
Then again, "secret gardens are better than walled gardens.")


-David


From nobody Wed Oct 29 20:41:09 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E8B1AD009 for <rtgwg@ietfa.amsl.com>; Wed, 29 Oct 2014 20:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 KkH_h3ZFDw2o for <rtgwg@ietfa.amsl.com>; Wed, 29 Oct 2014 20:41:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5FFC1AD003 for <rtgwg@ietf.org>; Wed, 29 Oct 2014 20:41:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOE96920; Thu, 30 Oct 2014 03:41:04 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 30 Oct 2014 03:41:03 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Thu, 30 Oct 2014 11:40:59 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVg==
Date: Thu, 30 Oct 2014 03:40:59 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/GAZhskzFqBMU11TJGj_9N3T90z4
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 03:41:07 -0000

Hi,

We have submitted a draft on router backdoor threat model. The main target =
is the threat model at the beginning. It is a little limited to the device =
level instead of the routing system level. Some threats are common to other=
 devices as well. We would like to know if there are people interested in t=
his work or can give some constructive comments or input. Any related discu=
ssion in the list or with the authors is welcome : )

Here is the link for the draft.
http://www.ietf.org/id/draft-song-router-backdoor-00.txt

Best Regards!
-Haibin




From nobody Thu Oct 30 11:35:08 2014
Return-Path: <uma.chunduri@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 165CF1A1A73 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 11:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 XrNpDDXAOyrB for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 11:35:04 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 376CA1A1A84 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 11:35:04 -0700 (PDT)
X-AuditID: c618062d-f79206d0000014d2-27-54522cc641db
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A6.94.05330.6CC22545; Thu, 30 Oct 2014 13:19:18 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Thu, 30 Oct 2014 14:35:02 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0g
Date: Thu, 30 Oct 2014 18:35:01 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyuXSPt+4xnaAQg81nDC02/rnLZnHhzW9m ByaPliNvWT2WLPnJFMAUxWWTkpqTWZZapG+XwJUx4/VytoKdnBU3Z65kbWC8zd7FyMkhIWAi 8bvnFwuELSZx4d56ti5GLg4hgSOMEvdnfYVyljNK3Nt4G6yKTUBP4uPUn2DdIgJBEsuOdzGD 2MICmhKv771l6mLkAIprSWw8XgNRYiRxd+M1ZpAwi4CqxLmDUSBhXgFfiWenbjOB2EICoRK3 z94Fm8gpECYxY/NUsE2MQPd8P7UGrIZZQFzi1pP5TBB3Ckgs2XOeGcIWlXj5+B8rhK0osa9/ OjtEvY7Egt2f2CBsbYllC18zQ+wVlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxcpQWp5bl phsZbGIExsIxCTbdHYx7XloeYhTgYFTi4S0oDAwRYk0sK67MPcQozcGiJM47q3ZesJBAemJJ anZqakFqUXxRaU5q8SFGJg5OqQZG6e2PU4tWvTumdCBhenFa5REF3nnvPqkrLWXaLiWtdsHm 4mRxj5fep1nNdVSsHz7QWKx+5vYT0Z+eDIteNolxNugkvLwQWWlborSebcHl9T/cuDn4e/i4 ji+ru1bw7ZP0gfb3d6dp/Fw0R/n16TPHr8ZN9ON1ZHTsWpAj9rEr49Ga70/TppptUWIpzkg0 1GIuKk4EAMqTZORmAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/6-aef3a2qM6Yv2ON4E8_YFFpZRE
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 18:35:06 -0000

If this is real, this is kind of byzantine attack and can be far more damag=
ing than what's being listed in this document.
Routing protocols security/Threat models generally discount this.=20

Is there any proof of detection of this kind of backdoors in operator netwo=
rks?
--
Uma C.


-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Songhaibin (A)
Sent: Wednesday, October 29, 2014 8:41 PM
To: rtgwg@ietf.org
Subject: Router backdoor threat model

Hi,

We have submitted a draft on router backdoor threat model. The main target =
is the threat model at the beginning. It is a little limited to the device =
level instead of the routing system level. Some threats are common to other=
 devices as well. We would like to know if there are people interested in t=
his work or can give some constructive comments or input. Any related discu=
ssion in the list or with the authors is welcome : )

Here is the link for the draft.
http://www.ietf.org/id/draft-song-router-backdoor-00.txt

Best Regards!
-Haibin



_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 14:19:21 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2A71A8823 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEkXpqVjRyu7 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:19:18 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F31211A87E9 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 14:19:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6AB5EA2; Thu, 30 Oct 2014 22:19:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1414703955; bh=7K9iL/9uV1d83aZQUDu9Q1BY6NaFftoV5q32a/4Eu7A=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=uhWCOqAIjMNa8XFZ0aW5rO0mmsNiId9M9HqB8DiJxTWblON1GjTexrpiZprYAwUbx S6PScttH9w1hCqzu2t7s5O2PtAkWpIROV7Pmer/UvNSC8j+i0CuShuypzoCkjxnYlE aVfRyI/YojtW2fJ8G7VSt7A2BGkDtvwQpPiD1zVk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 66613A1; Thu, 30 Oct 2014 22:19:15 +0100 (CET)
Date: Thu, 30 Oct 2014 22:19:15 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Uma Chunduri <uma.chunduri@ericsson.com>
Subject: RE: Router backdoor threat model
In-Reply-To: <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
Message-ID: <alpine.DEB.2.02.1410302207260.6420@uplift.swm.pp.se>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/b9bz1mxrxEQUyHOjXNuKsWcfLfM
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 21:19:19 -0000

On Thu, 30 Oct 2014, Uma Chunduri wrote:

> If this is real, this is kind of byzantine attack and can be far more damaging than what's being listed in this document.
> Routing protocols security/Threat models generally discount this.
>
> Is there any proof of detection of this kind of backdoors in operator networks?

http://www.infoworld.com/article/2608141/internet-privacy/snowden--the-nsa-planted-backdoors-in-cisco-products.html

This is a security question, I'm not sure the IETF is the best place to 
document these issues, even though it affects products that are used to 
implement IETF protocols. There is no doubt in my mind that there is a 
problem with all kinds of products being potentially backdoored, I have 
read enough papers on BIOS on motherboards, NICs etc being backdoored and 
end up running malicious software that is virtually impossible to detect 
and eradicate by an operator.

I don't know what to make of the document though, I think it depends on 
what its intended audience is. If it's supposed to make people aware of 
the potential problem, then it needs more facts and references to assure 
people that the problems described are real (because some will say it's 
not real until it's actually happened).

Another one where telecom functionality designed and implemented by 
government request was used in another fashion is 
<http://en.wikipedia.org/wiki/Greek_wiretapping_case_2004%E2%80%9305>. 
Here the LI function (which some government require to be invisible to the 
normal operator) was used to spy on some phones. You can probably get more 
detailed information internally from your colleagues about that one, 
compared to what is publically available.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Oct 30 14:45:48 2014
Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C37C51A8843 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ANnP7MqeUVnr for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:45:45 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A71EC1A8840 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 14:45:45 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-78-5452570d93c9
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 76.45.25146.D0752545; Thu, 30 Oct 2014 16:19:42 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0174.001; Thu, 30 Oct 2014 17:45:44 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: Uma Chunduri <uma.chunduri@ericsson.com>, "Songhaibin (A)" <haibin.song@huawei.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0gAAbHjYA=
Date: Thu, 30 Oct 2014 21:45:43 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
In-Reply-To: <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyuXRPiC5feFCIwcQr3BYb/9xls7jw5jez A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4MrYePAoU8Fs/oqWx/tYGxi38nQxcnJICJhI PL3fyQZhi0lcuLceyObiEBI4wiix/VgjK4SznFFi5bI+dpAqNgELicvfnjKD2CICNRI3Py9n AbGFBTQlXt97y9TFyAEU15LYeLwGosRK4ualhWDlLAKqEsv3/wazeQW8JVZuvsYCMX8mo8Sb 5feYQBKcAn4S55d0M4LYjEAXfT+1BizOLCAucevJfCaISwUkluw5zwxhi0q8fPyPFcJWkpi0 9BwrRL2OxILdn9ggbG2JZQtfQy0WlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxcpQWp5bl phsZbmIExsMxCTbHHYwLPlkeYhTgYFTi4S0oDAwRYk0sK67MPcQozcGiJM6rWT0vWEggPbEk NTs1tSC1KL6oNCe1+BAjEwenVAPjjHkb0m88OHXV8lhq7dH4GU0Vulql/dennLb/qyqzwC56 5ST5+cJu82/fEt260orJ931qr6flzcViPce3p03vu/nsddmyprIPdRbaUpn6+u+2HuYv+61w 0kmJL3i3r/OpyW7J8/7XGYX+yQo/YfbK6/rEjWdL69wm390ocY/fw2HZVj8Zwc+tSizFGYmG WsxFxYkAg8HbRGgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Q6ZmLuvVGrJBF9J-TjYpZhDco3c
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 21:45:47 -0000

That's actually a draft documenting the only real feature Huwaei implemente=
d in their product line after they assimilated in accelerated fashion some =
routing code they found by chance 10+ years ago :-P

Issue is well-known since couple years.=20

-- tony

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Uma Chunduri
> Sent: Thursday, October 30, 2014 11:35 AM
> To: Songhaibin (A); rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> If this is real, this is kind of byzantine attack and can be far more dam=
aging
> than what's being listed in this document.
> Routing protocols security/Threat models generally discount this.
>=20
> Is there any proof of detection of this kind of backdoors in operator
> networks?
> --
> Uma C.
>=20
>=20
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Songhaibin (A)
> Sent: Wednesday, October 29, 2014 8:41 PM
> To: rtgwg@ietf.org
> Subject: Router backdoor threat model
>=20
> Hi,
>=20
> We have submitted a draft on router backdoor threat model. The main
> target is the threat model at the beginning. It is a little limited to th=
e device
> level instead of the routing system level. Some threats are common to oth=
er
> devices as well. We would like to know if there are people interested in =
this
> work or can give some constructive comments or input. Any related
> discussion in the list or with the authors is welcome : )
>=20
> Here is the link for the draft.
> http://www.ietf.org/id/draft-song-router-backdoor-00.txt
>=20
> Best Regards!
> -Haibin
>=20
>=20
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 14:59:07 2014
Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA2C1A8859 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 AeWXh9s5zoDP for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 14:59:04 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5A631A8854 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 14:59:04 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-b4-54525a2c55ba
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 37.D5.25146.C2A52545; Thu, 30 Oct 2014 16:33:01 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0174.001; Thu, 30 Oct 2014 17:59:03 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: Antoni Przygienda <antoni.przygienda@ericsson.com>, Uma Chunduri <uma.chunduri@ericsson.com>, "Songhaibin (A)" <haibin.song@huawei.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0gAAbHjYAAAHfeQA==
Date: Thu, 30 Oct 2014 21:59:02 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F181D2D43@eusaamb103.ericsson.se>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se>
In-Reply-To: <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyuXRPuK5uVFCIwcx7bBYb/9xls7jw5jez A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mp48uIwa0EDW8W1v+uZGhjfsHQxcnBICJhI vPsl2cXICWSKSVy4t54NxBYSOMIoseO1QxcjF5C9nFHi88PpYAk2AQuJy9+eMoMkRAQ2MUpM mbSZBSQhLKAp8freWyaQoSICWhIbj9eAhEUEnCRebjnACmKzCKhKXJ5wkhnE5hXwltixaR4L xILbjBLbZ34HK+IU8JFY1bEczGYEuuj7qTVMIDazgLjErSfzmSAuFZBYsuc8M4QtKvHy8T9W CFtJYtLSc6wQ9ToSC3Z/YoOwtSWWLXwNtVhQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcXI UVqcWpabbmS4iREYDcck2Bx3MC74ZHmIUYCDUYmHt6AwMESINbGsuDL3EKM0B4uSOK9m9bxg IYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxhktziJZvs6nUsKwxEVQzdHZVn1cfaehczHXlm 5KVzwVxMwK0uI7XaoapZluHO3rOlybs953MveSQ6/+7KiVPDFy+cM5VBNdIv/nf1NqsiL9uf QrPeszQq5gYtuB4841Bd3M5nKp/187Yy6XizugbOMEqNPVr3V7W2Y4OgzOPmfxM0Hvx6rMRS nJFoqMVcVJwIAF2fG65nAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/zk_TONQhE0GL4zqukZhklHIG8qo
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 21:59:06 -0000

ouch, that was obviously intended as a joke and escaped the intended distri=
bution list. =20

thoroughly sorry for that guys, should have known after all those years tha=
t  reply-all: is a bug and not a mailer feature

--- tony=20

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Antoni
> Przygienda
> Sent: Thursday, October 30, 2014 2:46 PM
> To: Uma Chunduri; Songhaibin (A); rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> That's actually a draft documenting the only real feature Huwaei
> implemented in their product line after they assimilated in accelerated
> fashion some routing code they found by chance 10+ years ago :-P
>=20
> Issue is well-known since couple years.
>=20


From nobody Thu Oct 30 15:01:45 2014
Return-Path: <adam.vitkovsky@swan.sk>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFE91A883E for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 15:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.406
X-Spam-Level: 
X-Spam-Status: No, score=-0.406 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IffIFGXy332 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 15:01:42 -0700 (PDT)
Received: from mail.swan.sk (owa.swan.sk [217.75.72.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1A631A876B for <rtgwg@ietf.org>; Thu, 30 Oct 2014 15:01:41 -0700 (PDT)
From: =?iso-8859-2?Q?Vitkovsk=FD_Adam?= <adam.vitkovsky@swan.sk>
To: "Songhaibin (A)" <haibin.song@huawei.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAlzkQg
Date: Thu, 30 Oct 2014 22:01:39 +0000
Message-ID: <61DC6BC4ABA10E4489D4A73EBABAC18B19F5C617@EX01.swan.local>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com>
Accept-Language: sk-SK, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.44.10]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/agLpytFAH5hi3yNSu7XlZkIoUyA
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 22:01:44 -0000

Hi folks,

At least Cisco went public with the whole lawful-intercept thing though the=
 actual functionality is not explained:=20
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/l=
awful/intercept/book/65LIch1.html
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-1/se=
curity/configuration/guide/b_syssec_cg41asr9k/b_syssec_cg41asr9k_chapter_01=
1.html

It's a good think we can disable the functionality with "lawful-intercept d=
isable", but oh wait we can't no more on the recent XR version.=20
Since the lawful-intercept disable is now hidden/unavailable may I assume t=
he necessary SNMP configs to public government IPs are hidden as well?=20

=20
adam
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Songhaibin (A)
> Sent: Thursday, October 30, 2014 4:41 AM
> To: rtgwg@ietf.org
> Subject: Router backdoor threat model
>=20
> Hi,
>=20
> We have submitted a draft on router backdoor threat model. The main targe=
t is
> the threat model at the beginning. It is a little limited to the device l=
evel
> instead of the routing system level. Some threats are common to other dev=
ices
> as well. We would like to know if there are people interested in this wor=
k or
> can give some constructive comments or input. Any related discussion in t=
he list
> or with the authors is welcome : )
>=20
> Here is the link for the draft.
> http://www.ietf.org/id/draft-song-router-backdoor-00.txt
>=20
> Best Regards!
> -Haibin
>=20
>=20
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 21:07:23 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C97A1A8A9E for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 21:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tlYJemIKSxjo for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 21:07:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F2C61A8A94 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 21:07:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOG12236; Fri, 31 Oct 2014 04:07:11 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Oct 2014 04:07:10 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 31 Oct 2014 12:07:04 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Antoni Przygienda <antoni.przygienda@ericsson.com>, Uma Chunduri <uma.chunduri@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0gAAbHjYAAAHfeQAAM0IbA
Date: Fri, 31 Oct 2014 04:07:03 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0B64@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D43@eusaamb103.ericsson.se>
In-Reply-To: <2E4BB27CAB87BF43B4207C0E55860F181D2D43@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/3TBGH5STEWCDQTiOc0ku5WUmsr0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 04:07:15 -0000

This is a ridiculous joke which is not funny at all.

Best Regards!
-Haibin


> -----Original Message-----
> From: Antoni Przygienda [mailto:antoni.przygienda@ericsson.com]
> Sent: Friday, October 31, 2014 5:59 AM
> To: Antoni Przygienda; Uma Chunduri; Songhaibin (A); rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> ouch, that was obviously intended as a joke and escaped the intended
> distribution list.
>=20
> thoroughly sorry for that guys, should have known after all those years t=
hat
> reply-all: is a bug and not a mailer feature
>=20
> --- tony
>=20
> > -----Original Message-----
> > From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Antoni
> > Przygienda
> > Sent: Thursday, October 30, 2014 2:46 PM
> > To: Uma Chunduri; Songhaibin (A); rtgwg@ietf.org
> > Subject: RE: Router backdoor threat model
> >
> > That's actually a draft documenting the only real feature Huwaei
> > implemented in their product line after they assimilated in
> > accelerated fashion some routing code they found by chance 10+ years
> > ago :-P
> >
> > Issue is well-known since couple years.
> >


From nobody Thu Oct 30 21:58:51 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF691A8AAF for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 21:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 OI0sZzId3Gdh for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 21:58:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D6461A8AAA for <rtgwg@ietf.org>; Thu, 30 Oct 2014 21:58:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLD09585; Fri, 31 Oct 2014 04:58:45 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Oct 2014 04:58:44 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Fri, 31 Oct 2014 12:58:40 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: =?iso-8859-1?Q?Vitkovsk=FD_Adam?= <adam.vitkovsky@swan.sk>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAlzkQgAA8BoiA=
Date: Fri, 31 Oct 2014 04:58:39 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0BA0@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <61DC6BC4ABA10E4489D4A73EBABAC18B19F5C617@EX01.swan.local>
In-Reply-To: <61DC6BC4ABA10E4489D4A73EBABAC18B19F5C617@EX01.swan.local>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/astEO6r6Fxi8YnW6F1403raikDk
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 04:58:49 -0000

Hi Adam,

I think technical specifications cannot go beyond laws. Since IMO lawful in=
terception is required by laws in most countries in the world, we cannot pr=
otect communication from LI. I guess what we should avoid is the man in the=
 middle attack.

Best Regards!
-Haibin


> -----Original Message-----
> From: Vitkovsk=FD Adam [mailto:adam.vitkovsky@swan.sk]
> Sent: Friday, October 31, 2014 6:02 AM
> To: Songhaibin (A); rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> Hi folks,
>=20
> At least Cisco went public with the whole lawful-intercept thing though t=
he
> actual functionality is not explained:
> http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX=
/
> lawful/intercept/book/65LIch1.html
> http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-1/
> security/configuration/guide/b_syssec_cg41asr9k/b_syssec_cg41asr9k_chapte
> r_011.html
>=20
> It's a good think we can disable the functionality with "lawful-intercept=
 disable",
> but oh wait we can't no more on the recent XR version.
> Since the lawful-intercept disable is now hidden/unavailable may I assume=
 the
> necessary SNMP configs to public government IPs are hidden as well?
>=20
>=20
> adam
> > -----Original Message-----
> > From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Songhaibin
> > (A)
> > Sent: Thursday, October 30, 2014 4:41 AM
> > To: rtgwg@ietf.org
> > Subject: Router backdoor threat model
> >
> > Hi,
> >
> > We have submitted a draft on router backdoor threat model. The main
> > target is the threat model at the beginning. It is a little limited to
> > the device level instead of the routing system level. Some threats are
> > common to other devices as well. We would like to know if there are
> > people interested in this work or can give some constructive comments
> > or input. Any related discussion in the list or with the authors is
> > welcome : )
> >
> > Here is the link for the draft.
> > http://www.ietf.org/id/draft-song-router-backdoor-00.txt
> >
> > Best Regards!
> > -Haibin
> >
> >
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 22:01:56 2014
Return-Path: <fred@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54AE01A8AAA for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 5CpEsoz_y3dC for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:01:51 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DD211A8AB4 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 22:01:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1033; q=dns/txt; s=iport; t=1414731709; x=1415941309; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Tbq+5a69CCvgTYz2BBYo42cgcwRNdrY29ZUDl1pi6Co=; b=LS9/A777f/gd1/1bshX1C61TFMmdSe+Kcdt3ALiWhuYILTkYQlC4XbsJ rqZfo4zw+E8+yv07awbXPNZI9g4h+bYRwZl007tP+QtAVdoGfVkx0gsC3 Uv8VaGSwvPyknkgLZbC4LsMOUprUPhgdZbUDLASfEdUubEeZTVE/R0ovA I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAKQWU1StJV2P/2dsb2JhbABcgw6BKwTUJgKBGxYBfYQDAQEDAXkFCwIBCEYyJQEBBA4FDogpCMlgAQEBAQEBAQEBAQEBAQEBAQEBAQEBF5BRB4MtgR4BBI9lghyCDoFQh3uWIoN3bIFIgQMBAQE
X-IronPort-AV: E=Sophos;i="5.07,292,1413244800";  d="asc'?scan'208";a="364964472"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-1.cisco.com with ESMTP; 31 Oct 2014 05:01:49 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9V51mp9018044 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Oct 2014 05:01:48 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.248]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Fri, 31 Oct 2014 00:01:48 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>
Subject: Re: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAlzkQgAA8BoiAACsgZAA==
Date: Fri, 31 Oct 2014 05:01:48 +0000
Message-ID: <9E8D4715-52B5-4243-BE0F-AFB3EBE51FEF@cisco.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <61DC6BC4ABA10E4489D4A73EBABAC18B19F5C617@EX01.swan.local> <E33E01DFD5BEA24B9F3F18671078951F651A0BA0@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F651A0BA0@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: multipart/signed; boundary="Apple-Mail=_DC69AF59-BAA5-4CDF-86AA-677D7DB0BDBE"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/4IxPFL7synu7rk-Rfa8Mj9T_Klc
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 05:01:53 -0000

--Apple-Mail=_DC69AF59-BAA5-4CDF-86AA-677D7DB0BDBE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 30, 2014, at 9:58 PM, Songhaibin (A) <haibin.song@huawei.com> =
wrote:

> I think technical specifications cannot go beyond laws. Since IMO =
lawful interception is required by laws in most countries in the world, =
we cannot protect communication from LI. I guess what we should avoid is =
the man in the middle attack.

Pretty much.

--Apple-Mail=_DC69AF59-BAA5-4CDF-86AA-677D7DB0BDBE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUUxfAbjEdbHIsm0MRAhl7AKC3uKdjYEL8HETIwOT5CTcgLZiw8wCg1GAC
Jtyo0eS6AYVCR2Lq1w9lL2M=
=BGpP
-----END PGP SIGNATURE-----

--Apple-Mail=_DC69AF59-BAA5-4CDF-86AA-677D7DB0BDBE--


From nobody Thu Oct 30 22:17:59 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D30E1A8AB5 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ur7svKnkbU5k for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:17:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0C741A8AB3 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 22:17:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOG16426; Fri, 31 Oct 2014 05:17:53 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Oct 2014 05:17:52 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 31 Oct 2014 13:17:47 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Uma Chunduri <uma.chunduri@ericsson.com>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0g//+pIYD//vbQIA==
Date: Fri, 31 Oct 2014 05:17:46 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0BBB@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <alpine.DEB.2.02.1410302207260.6420@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1410302207260.6420@uplift.swm.pp.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/tuibZ0guo3KUCn26LoMH5XGDf1k
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 05:17:58 -0000

Hi Mikael,

The motivation is that router vendors (with global market) are more or less=
 doubted with security concerns when doing international business. If we ca=
n give a clear potential threat model on how it works when committing a mal=
icious eavesdropping or something else, and a guidance on how to avoid the =
problem or protect the communication, then it will help to mitigate those s=
ecurity concerns (I do not say fully, but more or less).

I do not see the facts of router backdoors, even in the event of PRISM, the=
 backdoor is not from the vendor either.=20

Best Regards!
-Haibin


> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Mikael
> Abrahamsson
> Sent: Friday, October 31, 2014 5:19 AM
> To: Uma Chunduri
> Cc: rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> On Thu, 30 Oct 2014, Uma Chunduri wrote:
>=20
> > If this is real, this is kind of byzantine attack and can be far more d=
amaging
> than what's being listed in this document.
> > Routing protocols security/Threat models generally discount this.
> >
> > Is there any proof of detection of this kind of backdoors in operator n=
etworks?
>=20
> http://www.infoworld.com/article/2608141/internet-privacy/snowden--the-ns=
a
> -planted-backdoors-in-cisco-products.html
>=20
> This is a security question, I'm not sure the IETF is the best place to d=
ocument
> these issues, even though it affects products that are used to implement =
IETF
> protocols. There is no doubt in my mind that there is a problem with all =
kinds of
> products being potentially backdoored, I have read enough papers on BIOS =
on
> motherboards, NICs etc being backdoored and end up running malicious
> software that is virtually impossible to detect and eradicate by an opera=
tor.
>=20
> I don't know what to make of the document though, I think it depends on w=
hat
> its intended audience is. If it's supposed to make people aware of the po=
tential
> problem, then it needs more facts and references to assure people that th=
e
> problems described are real (because some will say it's not real until it=
's
> actually happened).
>=20
> Another one where telecom functionality designed and implemented by
> government request was used in another fashion is
> <http://en.wikipedia.org/wiki/Greek_wiretapping_case_2004%E2%80%9305>.
> Here the LI function (which some government require to be invisible to th=
e
> normal operator) was used to spy on some phones. You can probably get mor=
e
> detailed information internally from your colleagues about that one, comp=
ared
> to what is publically available.
>=20
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 22:23:18 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447A81A8AAA for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 mw9CFQOvf2Vw for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 22:23:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2B001A8AB7 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 22:23:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLD10883; Fri, 31 Oct 2014 05:23:09 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Oct 2014 05:23:08 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Fri, 31 Oct 2014 13:23:05 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Uma Chunduri <uma.chunduri@ericsson.com>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0g//+pIYD//vNjUA==
Date: Fri, 31 Oct 2014 05:23:04 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0BCF@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <alpine.DEB.2.02.1410302207260.6420@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1410302207260.6420@uplift.swm.pp.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Yhf2pAiTr3C27LnPq3XnRhPVlSQ
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 05:23:15 -0000

There was TCP 32764 backdoor reported on home routers. But telecom routers =
are actually much more secure and I do not see any backdoor report.

Best Regards!
-Haibin


> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Mikael
> Abrahamsson
> Sent: Friday, October 31, 2014 5:19 AM
> To: Uma Chunduri
> Cc: rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> On Thu, 30 Oct 2014, Uma Chunduri wrote:
>=20
> > If this is real, this is kind of byzantine attack and can be far more d=
amaging
> than what's being listed in this document.
> > Routing protocols security/Threat models generally discount this.
> >
> > Is there any proof of detection of this kind of backdoors in operator n=
etworks?
>=20
> http://www.infoworld.com/article/2608141/internet-privacy/snowden--the-ns=
a
> -planted-backdoors-in-cisco-products.html
>=20
> This is a security question, I'm not sure the IETF is the best place to d=
ocument
> these issues, even though it affects products that are used to implement =
IETF
> protocols. There is no doubt in my mind that there is a problem with all =
kinds of
> products being potentially backdoored, I have read enough papers on BIOS =
on
> motherboards, NICs etc being backdoored and end up running malicious
> software that is virtually impossible to detect and eradicate by an opera=
tor.
>=20
> I don't know what to make of the document though, I think it depends on w=
hat
> its intended audience is. If it's supposed to make people aware of the po=
tential
> problem, then it needs more facts and references to assure people that th=
e
> problems described are real (because some will say it's not real until it=
's
> actually happened).
>=20
> Another one where telecom functionality designed and implemented by
> government request was used in another fashion is
> <http://en.wikipedia.org/wiki/Greek_wiretapping_case_2004%E2%80%9305>.
> Here the LI function (which some government require to be invisible to th=
e
> normal operator) was used to spy on some phones. You can probably get mor=
e
> detailed information internally from your colleagues about that one, comp=
ared
> to what is publically available.
>=20
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Oct 30 23:17:15 2014
Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D981A8AC6 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 23:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Qfhy8ViSqC00 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 23:17:08 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E479D1A8AC5 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 23:17:07 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-2a-5452cee24062
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 27.00.25146.2EEC2545; Fri, 31 Oct 2014 00:50:59 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Fri, 31 Oct 2014 02:17:05 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0gAAbHjYAAAHfeQAAM0IbAAASLNhA=
Date: Fri, 31 Oct 2014 06:17:04 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F181D32ED@eusaamb103.ericsson.se>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D43@eusaamb103.ericsson.se> <E33E01DFD5BEA24B9F3F18671078951F651A0B64@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F651A0B64@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyuXSPt+7jc0EhBi9+C1hs/HOXzeLCm9/M DkweLUfesnosWfKTKYApissmJTUnsyy1SN8ugSvjzvrJ7AW7WCumbzvJ1MC4jqWLkYNDQsBE 4u+CoC5GTiBTTOLCvfVsILaQwBFGiVfzg7sYuYDs5YwSM5b+ZgJJsAlYSFz+9pQZxBYRCJJY drwLzBYW0JR4fe8tE8hMEQEtiY3HayBMP4nnc/NBKlgEVCXe7trJDmLzCnhL7LoxmRli/Esm ifmHp4ON5xQIk1j+/iZYESPQPd9PrQGLMwuIS9x6Mp8J4k4BiSV7zjND2KISLx//Y4WwlSQm LT3HClGvI7Fg9yc2CFtbYtnC18wQiwUlTs58wjKBUXQWkrGzkLTMQtIyC0nLAkaWVYwcpcWp ZbnpRoabGIGRcEyCzXEH44JPlocYBTgYlXh4PxwKChFiTSwrrsw9xCjNwaIkzqtZPS9YSCA9 sSQ1OzW1ILUovqg0J7X4ECMTB6dUA+PcVclNCslVr458CfiweU+Bzc/D96t5l3X2HKxm951x 44RkzClRlhblj59nsLec6b7CHeO2TDieO3LZlLpXL3yWlpXdE3Lr510vLW7tfEE4IviEVo/K oitSIi8O+fHu8nHaFc4/73ah/pF4tUa+G7OvP1+Rwv63cpmtlsFrB/+bh548XdZq81aJpTgj 0VCLuag4EQAM6LpXZQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/gtagmYBGtFTPvgT_nKO8mWbaBgg
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 06:17:10 -0000

I would like to express with this email again a sincere apology to the=20
authors of the draft and any company or individual whose feelings may=20
have been hurt by the slip in the email communication from my side=20
today. I hope that the author who offered to accept this apology=20
is magnanimous enough to do so.

thanks=20

--- tony=20

> -----Original Message-----
> From: Songhaibin (A) [mailto:haibin.song@huawei.com]
> Sent: Thursday, October 30, 2014 9:07 PM
> To: Antoni Przygienda; Uma Chunduri; rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
>=20
> This is a ridiculous joke which is not funny at all.
>=20
> Best Regards!
> -Haibin
>=20
>=20


From nobody Thu Oct 30 23:24:50 2014
Return-Path: <haibin.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 837F81A8AC0 for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 23:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fUqLfKrahpuc for <rtgwg@ietfa.amsl.com>; Thu, 30 Oct 2014 23:24:46 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BD9B1A00E2 for <rtgwg@ietf.org>; Thu, 30 Oct 2014 23:24:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLD14551; Fri, 31 Oct 2014 06:24:43 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Oct 2014 06:24:41 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Fri, 31 Oct 2014 14:24:36 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Antoni Przygienda <antoni.przygienda@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Router backdoor threat model
Thread-Topic: Router backdoor threat model
Thread-Index: Ac/z81GOqJ5a0WD4ShecsKIyTbiLVgAfDf0gAAbHjYAAAHfeQAAM0IbAAASLNhAAAD4pQA==
Date: Fri, 31 Oct 2014 06:24:35 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F651A0C4B@nkgeml501-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D05@eusaamb103.ericsson.se> <2E4BB27CAB87BF43B4207C0E55860F181D2D43@eusaamb103.ericsson.se> <E33E01DFD5BEA24B9F3F18671078951F651A0B64@nkgeml501-mbs.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F181D32ED@eusaamb103.ericsson.se>
In-Reply-To: <2E4BB27CAB87BF43B4207C0E55860F181D32ED@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/KeLbK38XfvDxuCj8rhrpMWByFAU
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 06:24:47 -0000

Tony,

Accepted.

-Haibin


> -----Original Message-----
> From: Antoni Przygienda [mailto:antoni.przygienda@ericsson.com]
> Sent: Friday, October 31, 2014 2:17 PM
> To: Songhaibin (A); rtgwg@ietf.org
> Subject: RE: Router backdoor threat model
>=20
> I would like to express with this email again a sincere apology to the au=
thors of
> the draft and any company or individual whose feelings may have been hurt=
 by
> the slip in the email communication from my side today. I hope that the a=
uthor
> who offered to accept this apology is magnanimous enough to do so.
>=20
> thanks
>=20
> --- tony
>=20
> > -----Original Message-----
> > From: Songhaibin (A) [mailto:haibin.song@huawei.com]
> > Sent: Thursday, October 30, 2014 9:07 PM
> > To: Antoni Przygienda; Uma Chunduri; rtgwg@ietf.org
> > Subject: RE: Router backdoor threat model
> >
> >
> > This is a ridiculous joke which is not funny at all.
> >
> > Best Regards!
> > -Haibin
> >
> >


From nobody Fri Oct 31 11:03:20 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC63A1A037B for <rtgwg@ietfa.amsl.com>; Fri, 31 Oct 2014 11:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 7uznP-Ad2qKe for <rtgwg@ietfa.amsl.com>; Fri, 31 Oct 2014 11:03:17 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFFF1A0101 for <rtgwg@ietf.org>; Fri, 31 Oct 2014 11:03:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1854; q=dns/txt; s=iport; t=1414778596; x=1415988196; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=H+uS4LYN9fiUvmN1tgqhNZ4TovlrQpFw9ee+Vy0dA30=; b=NBPx/YsNbzgGWMhi+sUokaBrWYRVMg3Ck5waMtRgAIz9pStalAsp3zaL 11hwJgxp16YW/kZWyYeFbovSHJsgsnnyl8k77dBuiTr4EK5LWb3BVDrzm T5wfYZgd66osUASpLWUFDgOuC6YEIW6WCCR8Pv17bwQ82yWILqkFGVTcv M=;
X-IronPort-AV: E=Sophos;i="5.07,295,1413244800"; d="scan'208";a="92207358"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-2.cisco.com with ESMTP; 31 Oct 2014 18:03:16 +0000
Received: from [64.103.108.173] (dhcp-bdlk10-data-vlan301-64-103-108-173.cisco.com [64.103.108.173]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s9VI3F8q017459; Fri, 31 Oct 2014 18:03:15 GMT
Message-ID: <5453CEE4.2070305@cisco.com>
Date: Fri, 31 Oct 2014 18:03:16 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Router backdoor threat model
References: <E33E01DFD5BEA24B9F3F18671078951F651A0772@nkgeml501-mbs.china.huawei.com> <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
In-Reply-To: <1B502206DFA0C544B7A60469152008633F3FE71C@eusaamb105.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/joA5Apbx2z5lDGvyT8bc0_LW2WA
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
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: <http://www.ietf.org/mail-archive/web/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, 31 Oct 2014 18:03:18 -0000

For much of this you could cross out router and write in host.

It all applies to many networking functions other that routers such as 
switches, firewalls, NFV functions etc.

I am not convinced that RTGWG is the right place for this, a good case 
could be made for OPSWG or somewhere in SEC.

Stewart

On 30/10/2014 18:35, Uma Chunduri wrote:
> If this is real, this is kind of byzantine attack and can be far more damaging than what's being listed in this document.
> Routing protocols security/Threat models generally discount this.
>
> Is there any proof of detection of this kind of backdoors in operator networks?
> --
> Uma C.
>
>
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Songhaibin (A)
> Sent: Wednesday, October 29, 2014 8:41 PM
> To: rtgwg@ietf.org
> Subject: Router backdoor threat model
>
> Hi,
>
> We have submitted a draft on router backdoor threat model. The main target is the threat model at the beginning. It is a little limited to the device level instead of the routing system level. Some threats are common to other devices as well. We would like to know if there are people interested in this work or can give some constructive comments or input. Any related discussion in the list or with the authors is welcome : )
>
> Here is the link for the draft.
> http://www.ietf.org/id/draft-song-router-backdoor-00.txt
>
> Best Regards!
> -Haibin
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html

