
From tkirkham@anthony-kirkham.com  Sun Apr  1 20:03:05 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5696421F86F4 for <grow@ietfa.amsl.com>; Sun,  1 Apr 2012 20:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.201
X-Spam-Level: *
X-Spam-Status: No, score=1.201 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hy5c-ZnpIhso for <grow@ietfa.amsl.com>; Sun,  1 Apr 2012 20:03:04 -0700 (PDT)
Received: from nskntmtas02p.mx.bigpond.com (nskntmtas02p.mx.bigpond.com [61.9.168.140]) by ietfa.amsl.com (Postfix) with ESMTP id F37BD21F86F2 for <grow@ietf.org>; Sun,  1 Apr 2012 20:03:03 -0700 (PDT)
Received: from nskntcmgw09p ([61.9.169.169]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20120402030302.UCBX24575.nskntmtas02p.mx.bigpond.com@nskntcmgw09p>;  Mon, 2 Apr 2012 03:03:02 +0000
Received: from Anthonys-MacBook-Pro.local ([124.187.92.14]) by nskntcmgw09p with BigPond Outbound id sr2z1i00Y0JbYsC01r30GV; Mon, 02 Apr 2012 03:03:02 +0000
X-Authority-Analysis: v=2.0 cv=CZqKFcXl c=1 sm=1 a=eckBsgz14t+FqcypcVY6Mg==:17 a=Vy4kjOWDvb4A:10 a=BdgN1ciYLZcA:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=kj9zAlcOel0A:10 a=ahv8dbORAAAA:8 a=48vgC7mUAAAA:8 a=5ojWulcyuCOs1YM8sKAA:9 a=kMOcWtM4RJbOioXNU30A:7 a=CjuIK1q_8ugA:10 a=BDsChg1p1CEA:10 a=lZB815dzVvQA:10 a=TexY256ddOLKX0lA:21 a=e4N4k9ERCBlo4Q_W:21 a=eckBsgz14t+FqcypcVY6Mg==:117
Message-ID: <4F7916E3.6070405@anthony-kirkham.com>
Date: Mon, 02 Apr 2012 13:02:59 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com> <006501cd0f28$bb177e80$4001a8c0@gateway.2wire.net>
In-Reply-To: <006501cd0f28$bb177e80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] draft-behringer-lla-only anddraft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 03:03:05 -0000

Tom,

Thank you for your update and support. I will incorporate your earlier 
comments in the next week or so.

Also, thanks to Wes George for his review and comments.

Personally, I'd like to see the draft get approved and published as an 
RFC. From various peoples comments to me, I understand the draft as it 
stands contains some information useful to the industry, particularly at 
this point in time. I don't believe there are any areas of dissent.

I do note that there have been some good ideas for improvement, in 
particular from Bruno Decraene (to incorporate a more in depth analysis 
of stolen IPs), and also the suggestion to include the equivalent 
analysis for IPv6 LLA. These are good ideas, however, will they will 
take more time to progress. My suggestion would be to perform these as 
follow on activities. I hope this makes sense.

Regards
Tony K





On 31/03/12 8:26 PM, t.petch wrote:
> ----- Original Message -----
> From: "George, Wes"<wesley.george@twcable.com>
> To:<grow@ietf.org>;<v6ops@ietf.org>
> Cc:<draft-behringer-lla-only@tools.ietf.org>
> Sent: Saturday, March 31, 2012 1:14 AM
>> Cross-posting to both lists again because I was unable to attend the v6ops
> session where draft-behringer was discussed, draft-ietf-grow-private-ip-sp-cores
> is likely nearing WGLC, and I believe that the issue I raised needs to be
> addressed before either proceeds. I defer to the chairs of both groups to
> determine how to manage this across the two groups.
>> After reviewing both draft-grow-private-ip-sp-cores (Kirkham) and
> draft-behringer-lla-only again, I am even more convinced that they either need
> to be merged, or that draft-behringer needs to be abandoned altogether as a bad
> idea. Draft-grow-private-ip-sp-cores is quite a lot more complete in its
> discussion of the considerations around private IP usage, but focuses on IPv4,
> meaning that it *is* incomplete for lack of discussion of IPv6, which is a
> reality in most SP cores today. Nearly all of the same considerations apply for
> IPv4 and IPv6 in this case, so there are probably a limited number of changes
> that would be necessary to cover IPv6 in the Kirkham document.
> <tp>
> Disagree.  As you say, the grow draft is more or less complete, more or less
> ready for WGLC.  And it has taken the IETF two years to get to this state.
>
> IPv6 is different.  We probably know little as yet as to how it works or how it
> should.
>
> Adding IPv6 would put this work back a year or two, and given that GROW is not
> the most lively of growps, it may never happen.
>
> Get the grow draft out as an RFC while it is still of value to its audience.
>
> Then contemplate a -bis with IPv6 if there is sufficient enthusiasm in a WG to
> do so.
>
> Tom Petch
>
>
>
>
>
>
>> I think that we need to come to some consensus on the recommended behavior on
> both cases. If the recommendation is different for one versus the other, we need
> to have a unified and clear articulation as to why this is the case. It may be
> that the consensus is to not recommend a behavior at all, and simply expand the
> format of Kirkham's document to cover any IPv6-specific items, since it
> discusses pros and cons evenly (as an informational doc) rather than
> recommending anything as a BCP. My vote is to do this, as I am unconvinced that
> use of LLA represents BCP today, nor should it. I outline some reasons below,
> but that's probably not as critical if others agree that this is the proper
> method to proceed with these documents.
>>
>>
>> If draft-behringer is left as a separate document, here are some specific
> comments:
>> The advantages proposed in draft-behringer are IMO not enough to justify
> recommending use of LLA.
>> - Smaller routing tables can be achieved through other methods such as setting
> the interfaces into passive mode in the IGP (so that they are not redistributed
> into the IGP) and/or not redistributing connected routes. Further, as SPs make
> great use of interface bundling (LAG), the number of interfaces with IP
> addresses is dramatically reduced, making the need to pull the point to point
> interfaces out of the routing table significantly lower.
>> - Reduced attack surface - draft-ietf-grow-private-ip-sp-cores sections 10 and
> 11 discuss this in great detail, and come to the conclusion that it is of
> limited benefit, and that alternatives exist to protect the infrastructure.
>> - lower configuration complexity - while this is true, it is replaced by
> additional complexity in troubleshooting. In the case of traces and pings
> locally on the box, it adds the additional step of requiring the operator to use
> extended ping and trace commands to specify the exit interface in order to make
> the ping work (vs simply issuing "ping [ip address]"), and makes it nearly
> impossible to derive the address of the remote interface without determining the
> remote side router through some other means and logging into the router to look.
> (vs practice today of using an IP in the same subnet, usually 1 digit up or down
> that can be guessed to save time).
>> - less address space: The other draft mentions this as well, in the context of
> IPv4 where it might make a difference, but this simply is not much of a concern
> with IPv6. An entire network could be numbered many times over out of one /64.
>> -simpler DNS : Most ISPs operating at the scale where this makes any
> difference at all have tools to build the DNS forward and reverse entries for
> their infrastructure automatically based on the router name and interface name
> extracted from their inventory tools. It's a few bits of scripting, so it's not
> like having less interfaces in DNS results in any net reduction in work or
> increase in the possibility of mistakes.
>> - Draft-ietf-grow-private-ip-sp-cores rightly notes that the proposed solution
> to broken pings/traces/PMTUD from draft-behringer (RFC 5837) has little or no
> implementation. This makes it a hard sell as any sort of recommended solution
> unless the benefits are much more significant than what is currently discussed
> in draft-behringer. This has to be a large enough benefit to justify pushing
> hard on router vendors to implement the feature and SPs to certify and deploy
> the code, and frankly there are many more important features to consider.
>> Thanks,
>>
>> Wes George
>>
>>
>>> -----Original Message-----
>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>>> internet-drafts@ietf.org
>>> Sent: Wednesday, March 28, 2012 7:21 AM
>>> To: i-d-announce@ietf.org
>>> Cc: grow@ietf.org
>>> Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories. This draft is a work item of the Global Routing Operations
>>> Working Group of the IETF.
>>>
>>>        Title           : Issues with Private IP Addressing in the Internet
>>>        Author(s)       : Anthony Kirkham
>>>        Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
>>>        Pages           : 15
>>>        Date            : 2012-03-28
>>>
>>>     The purpose of this document is to provide a discussion of the
>>>     potential problems of using private, RFC1918, or non-globally-
>>>     routable addressing within the core of an SP network.  The discussion
>>>     focuses on link addresses and to a small extent loopback addresses.
>>>     While many of the issues are well recognised within the ISP
>>>     community, there appears to be no document that collectively
>>>     describes the issues.
>>>
>>>
>>> A URL for this Internet-Draft is:
>>>
> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.txt
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> This Internet-Draft can be retrieved at:
>>>
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.txt
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely for the
> use of the individual or entity to which it is addressed. If you are not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may be
> unlawful. If you have received this E-mail in error, please notify the sender
> immediately and permanently delete the original and any copy of this E-mail and
> any printout.
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



From ietfc@btconnect.com  Thu Apr  5 13:00:52 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9880121F85AC for <grow@ietfa.amsl.com>; Thu,  5 Apr 2012 13:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-ZwWWt5YOnb for <grow@ietfa.amsl.com>; Thu,  5 Apr 2012 13:00:51 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id 7749D21F85AA for <grow@ietf.org>; Thu,  5 Apr 2012 13:00:50 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr10.btconnect.com with SMTP id GXL69209; Thu, 05 Apr 2012 21:00:49 +0100 (BST)
Message-ID: <001701cd135e$399daa20$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: <grow@ietf.org>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com><DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com> <006501cd0f28$bb177e80$4001a8c0@gateway.2wire.net>
Date: Thu, 5 Apr 2012 20:59:22 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F7DF9F0.007C, actions=tag
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.4.5.53315:17:8.317, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, SUBJ_1WORD, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4F7DF9F1.0029,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Subject: [GROW] test
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 20:00:52 -0000

much as I disapprove when people sent test messages to a list I need to know how
Badly Trashed my email service is as a result of unwanted and unwelcome changes
by my isp so I have succumbed

Tom Petch

> >
> > > -----Original Message-----
> > > From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> > > internet-drafts@ietf.org
> > > Sent: Wednesday, March 28, 2012 7:21 AM
> > > To: i-d-announce@ietf.org
> > > Cc: grow@ietf.org
> > > Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > > directories. This draft is a work item of the Global Routing Operations
> > > Working Group of the IETF.
> > >
> > >       Title           : Issues with Private IP Addressing in the Internet
> > >       Author(s)       : Anthony Kirkham
> > >       Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
> > >       Pages           : 15
> > >       Date            : 2012-03-28
> > >
> > >    The purpose of this document is to provide a discussion of the
> > >    potential problems of using private, RFC1918, or non-globally-
> > >    routable addressing within the core of an SP network.  The discussion
> > >    focuses on link addresses and to a small extent loopback addresses.
> > >    While many of the issues are well recognised within the ISP
> > >    community, there appears to be no document that collectively
> > >    describes the issues.
> > >
> > >
> > > A URL for this Internet-Draft is:
> > >
> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.txt
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > This Internet-Draft can be retrieved at:
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.txt
> > >
> > > _______________________________________________
> > > GROW mailing list
> > > GROW@ietf.org
> > > https://www.ietf.org/mailman/listinfo/grow
> >
> > This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely for
the
> use of the individual or entity to which it is addressed. If you are not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may be
> unlawful. If you have received this E-mail in error, please notify the sender
> immediately and permanently delete the original and any copy of this E-mail
and
> any printout.
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
> >
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>


From internet-drafts@ietf.org  Mon Apr  9 23:49:53 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67CC121F86FE; Mon,  9 Apr 2012 23:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTtpt+rD75U2; Mon,  9 Apr 2012 23:49:53 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C25821F8450; Mon,  9 Apr 2012 23:49:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120410064953.27574.88075.idtracker@ietfa.amsl.com>
Date: Mon, 09 Apr 2012 23:49:53 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 06:49:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Issues with Private IP Addressing in the Internet
	Author(s)       : Anthony Kirkham
	Filename        : draft-ietf-grow-private-ip-sp-cores-01.txt
	Pages           : 15
	Date            : 2012-04-09

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.=
txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.t=
xt


From rjs@rob.sh  Fri Apr 13 11:27:40 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB3011E8098 for <grow@ietfa.amsl.com>; Fri, 13 Apr 2012 11:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TGrH8rOb1y8 for <grow@ietfa.amsl.com>; Fri, 13 Apr 2012 11:27:39 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 62F1F11E8093 for <grow@ietf.org>; Fri, 13 Apr 2012 11:27:39 -0700 (PDT)
Received: from [109.144.237.160] (helo=[10.10.1.60]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SIlCw-0001hy-IZ; Fri, 13 Apr 2012 19:26:54 +0100
From: Rob Shakir <rjs@rob.sh>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Apr 2012 19:27:36 +0100
To: grow@ietf.org
Message-Id: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 18:27:40 -0000

Hi All,

I'd like to ask the WG their collective opinion on a couple of matters =
in this draft, which come from some discussions at IETF83 (in particular =
with John Scudder and Adam Simpson) about how the requirements are =
currently written regarding repeated errors.

The wording right now in the draft implies that at some point, the =
speaker that detects the failure could push the session into a "hold up" =
state ignoring any further UPDATE errors (i.e. at some point the =
'critical' error in the UPDATE is just ignored) and the prefixes that =
are are there are maintained.

   In the case of implementation errors, it is
   possible that the BGP session in question may enter a continuous loop
   of being reset, with a partial RIB being held by one or more of the
   BGP speakers due to an non-deterministic order of UPDATE propagation.
   It is therefore a requirement that within this reduced-impact
   procedure any subsequent UPDATE messages that would result in further
   session resets are ignored.  Whilst this results in a condition where
   an undetermined amount of the RIB is inconsistent, partial
   reachability is maintained.  In this case, the operational toolsets
   discussed in Section 6 is likely to provide mechanisms by which this
   condition can be brought to the attention of the relevant operators.
   This requirement to accept a partial RIB, which results in potential
   invalid traffic forwarding is a direct result of the deployments of
   BGP-4, as described in Section 1.1.

I think that actually, the discussions that I've had with various WG =
participants relating to this imply that at some point instead of =
ignoring the UPDATE, the session should be considered no longer viable, =
and the session ceased.

I think that the latter view is relevant only to Critical errors (i.e. =
those whereby the NLRI cannot be identified) that cause session reset - =
and that the implication should be at that at some point there is a =
requirement /not/ to continually keep applying the mechanisms that are =
specified in Section 5 of the draft. This is the behaviour that is =
implied in Section 7.1 of the draft.

The original wording of the draft did not draw a distinction between the =
behaviour expected for Semantic and Critical errors - which I think =
meant that the above recommendation was more relevant (one would not =
want to teardown based on errors that could be handled with =
treat-as-withdraw). Given that repeated Critical errors require repeated =
session-level error handling, this would seem to be indicative of a =
relatively long-lived failure (which is unlikely to recover) and hence =
at some point, continually performing hitless restarts becomes a futile =
exercise.

So, as such, given that there is an internal lack of consistency between =
these two sections - the suggestion I am proposing is to restructure =
Section 7 of the draft, such that it recommends:

- For Semantic errors, a staged recovery approach should be taken =
(should any automatic recovery be attempted) such that a specific =
recovery mechanism is implemented, in preference to re-requesting the =
entire RIB (so as to reduce the number of messages that are received).
- Where such Semantic errors are repeated, at some point (defined =
per-recovery mechanism memo or on a per-implementation basis based on =
the resource consumption of the recovery mechanism), no further =
automatic refresh action should be taken as a result of further Semantic =
errors. Such a condition should be flagged to an operator to flag this =
has taken place.
- For repeated Critical errors, an implementation maintains some =
"session badness" flag, which can be used to work out that the "hitless =
session restart" mechanisms (=A75) should no longer be applied. This =
condition should be flagged to an operator.
- There is no requirement within the "hitless session restart" mechanism =
to have any form of delay in terms of re-opening the session, since this =
must occur inside the time bound for the session restart described in =
Section 5.
- (As per John's suggestion) It is recommended that there is an =
exponential back-off for session re-establishment following the decision =
to stop using hitless restart procedures for a session (as per the =
existing definition for peer oscillation in RFC4271).

Is the WG in agreement with this recommendation, and restructuring of =
this section?

Many thanks,
r.




From tony.li@tony.li  Fri Apr 13 13:24:55 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6AA811E80BC for <grow@ietfa.amsl.com>; Fri, 13 Apr 2012 13:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=0.329, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxcZ9Aqq6-3g for <grow@ietfa.amsl.com>; Fri, 13 Apr 2012 13:24:55 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA0311E80E4 for <grow@ietf.org>; Fri, 13 Apr 2012 13:24:55 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta05.westchester.pa.mail.comcast.net with comcast id xXzn1i0010SCNGk55YQvyC; Fri, 13 Apr 2012 20:24:55 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta09.westchester.pa.mail.comcast.net with comcast id xYQj1i01S52qHCY3VYQmwM; Fri, 13 Apr 2012 20:24:53 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Tony Li <tony.li@tony.li>
In-Reply-To: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>
Date: Fri, 13 Apr 2012 13:24:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>
To: Rob Shakir <rjs@rob.sh>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 20:24:56 -0000

On Apr 13, 2012, at 11:27 AM, Rob Shakir wrote:

>   It is therefore a requirement that within this reduced-impact
>   procedure any subsequent UPDATE messages that would result in =
further
>   session resets are ignored.=20


Hi,

This may be a nit, but I think it's important to recall that UPDATE =
messages include withdrawn routes.  These MUST NOT be ignored by the =
receiver.  Doing so will simply result in forwarding loops or black =
holes.

Perhaps this should at least be wordsmithed into something like 'ignore =
any reachability information in an UPDATE message, while processing the =
withdrawn routes in that same UPDATE message'.




Independently of that, I think that trying to maintain a session in the =
face of multiple errors is a clear waste of time and effort on all =
parties.  At some point, there is more effort and complexity spent on =
error recovery than on correct transmission, and that's just backwards.  =
I support the suggestion of binary exponential back off on session =
restarts.

Regards,
Tony


From nick@inex.ie  Sun Apr 15 09:45:57 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A1321F879F for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 09:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.742
X-Spam-Level: 
X-Spam-Status: No, score=-1.742 tagged_above=-999 required=5 tests=[AWL=-0.858, BAYES_05=-1.11, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVrgkZwe1GeG for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 09:45:57 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id D84C321F877B for <grow@ietf.org>; Sun, 15 Apr 2012 09:45:56 -0700 (PDT)
X-Envelope-To: <grow@ietf.org>
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:d44a:90ff:f277:8188]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q3FGjfCL085822 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Sun, 15 Apr 2012 17:45:47 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4F8AFB3D.5030102@inex.ie>
Date: Sun, 15 Apr 2012 17:45:49 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
In-Reply-To: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
X-Enigmail-Version: 1.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Apr 2012 16:45:57 -0000

On 13/04/2012 21:24, Tony Li wrote:
> This may be a nit, but I think it's important to recall that UPDATE
> messages include withdrawn routes.  These MUST NOT be ignored by the
> receiver.  Doing so will simply result in forwarding loops or black
> holes.

I'm trying to figure out which is worse: accepting a semantically known
corrupt UPDATE withdraw message or ignoring it.  Also, I suspect that this
is getting into non-deterministic territory.  If you're seeing a continuous
stream of corrupt updates for different prefixes from a peer, that probably
indicates a more serious problem, for which session teardown might be a
more appropriate fix than ignoring broken nlri messages.

> Perhaps this should at least be wordsmithed into something like 'ignore
> any reachability information in an UPDATE message, while processing the
> withdrawn routes in that same UPDATE message'.

> Independently of that, I think that trying to maintain a session in the
> face of multiple errors is a clear waste of time and effort on all
> parties.

this is an important point: at what stage do you give up on a session?  The
draft has some discussion on this, but it might be useful to have a clearer
statement on what to do when you see a continuous stream of garbage.

Nick

From robert@raszuk.net  Sun Apr 15 20:06:47 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653F521F88ED for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojhG3gTiz4Ob for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:06:47 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 9D50621F88E8 for <grow@ietf.org>; Sun, 15 Apr 2012 20:06:46 -0700 (PDT)
Received: (qmail 28378 invoked by uid 399); 16 Apr 2012 03:06:46 -0000
Received: from unknown (HELO ?10.0.1.3?) (pbs:robert@raszuk.net@216.31.254.135) by mail1310.opentransfer.com with ESMTPM; 16 Apr 2012 03:06:46 -0000
X-Originating-IP: 216.31.254.135
Message-ID: <4F8B8CC5.9000906@raszuk.net>
Date: Mon, 16 Apr 2012 05:06:45 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
In-Reply-To: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:06:47 -0000

> Independently of that, I think that trying to maintain a session in
> the face of multiple errors is a clear waste of time and effort on
> all parties.  At some point, there is more effort and complexity
> spent on error recovery than on correct transmission, and that's just
> backwards.  I support the suggestion of binary exponential back off
> on session restarts.
>
> Regards, Tony

I would highly agree that the notion to keep the session at all cost is 
just a wrong thing to do.

Such notion comes often from the fact that operator did not provided 
path redundancy or are trigger by seemingly correct observation that 
single malformed update should not impact other correct updates received 
over the same session.

However neither the error handling IDR spec nor it's early 
implementations provide a way to still allow the reset to happen if X % 
of UPDATE messages in the window of time T sec are malformed.

Perhaps Rob's document as set of requirements could add such requirement 
to the spec ?

Regards,
R.

From jakob.heitz@ericsson.com  Sun Apr 15 20:22:12 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822C921F869C for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.326
X-Spam-Level: 
X-Spam-Status: No, score=-6.326 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JwFLydUcfv5v for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:22:12 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0B41921F8699 for <grow@ietf.org>; Sun, 15 Apr 2012 20:22:11 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q3G3MAb3001138 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 15 Apr 2012 22:22:11 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.157]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Sun, 15 Apr 2012 23:22:09 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "robert@raszuk.net" <robert@raszuk.net>, Tony Li <tony.li@tony.li>
Date: Sun, 15 Apr 2012 23:22:06 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0bffk63kdvFpfMR36yo9AONEK3UgAAFK5A
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net>
In-Reply-To: <4F8B8CC5.9000906@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:22:12 -0000

IMO
1. Error handling must be simple, lest we have to handle errors
of the error handling, ad infinitum...

2. Error handling should be restricted to error isolation
and reporting. It should refrain from attempting error recovery.

If an error can be isolated to a set of NLRI, withdraw them.
If an error can only be isolated to a session, reset it.

Tracking and analysing multiple errors to decide on a reset
violates point 1.

On Sunday, April 15, 2012 8:07 PM, Robert Raszuk <> wrote:

>> Independently of that, I think that trying to maintain a session in
>> the face of multiple errors is a clear waste of time and effort on
>> all parties.  At some point, there is more effort and complexity
>> spent on error recovery than on correct transmission, and that's just
>> backwards.  I support the suggestion of binary exponential back off
>> on session restarts.=20
>>=20
>> Regards, Tony
>=20
> I would highly agree that the notion to keep the session at all cost
> is just a wrong thing to do.
>=20
> Such notion comes often from the fact that operator did not provided
> path redundancy or are trigger by seemingly correct observation that
> single malformed update should not impact other correct updates
> received over the same session.
>=20
> However neither the error handling IDR spec nor it's early
> implementations provide a way to still allow the reset to happen if X
> % of UPDATE messages in the window of time T sec are malformed.
>=20
> Perhaps Rob's document as set of requirements could add such
> requirement to the spec ?
>=20
> Regards,
> R.

--=20
Jakob Heitz.=

From robert@raszuk.net  Sun Apr 15 20:33:41 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E0021F87C1 for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRL7yzdgJqaT for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:33:41 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 078F221F87B7 for <grow@ietf.org>; Sun, 15 Apr 2012 20:33:41 -0700 (PDT)
Received: (qmail 1757 invoked by uid 399); 16 Apr 2012 03:33:40 -0000
Received: from unknown (HELO ?10.0.1.3?) (pbs:robert@raszuk.net@216.31.254.135) by mail1310.opentransfer.com with ESMTPM; 16 Apr 2012 03:33:40 -0000
X-Originating-IP: 216.31.254.135
Message-ID: <4F8B9314.9030700@raszuk.net>
Date: Mon, 16 Apr 2012 05:33:40 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:33:41 -0000

Hi Jakob,

Just to make sure you got my point ...

I am not suggesting adding ton of logic and algorithmic operations.

All I am suggesting is simple counter (time drained) which would count 
how many times in a given period we are performing the treat-as-withdraw 
action.

Algorithm:
----------

If such counter get's exceeded session get's reset.

There is tracking (counter++ operation) and one additional conditional 
if statement. There is no analysis what so ever.

Best,
R.


> IMO
> 1. Error handling must be simple, lest we have to handle errors
> of the error handling, ad infinitum...
>
> 2. Error handling should be restricted to error isolation
> and reporting. It should refrain from attempting error recovery.
>
> If an error can be isolated to a set of NLRI, withdraw them.
> If an error can only be isolated to a session, reset it.
>
> Tracking and analysing multiple errors to decide on a reset
> violates point 1.
>
> On Sunday, April 15, 2012 8:07 PM, Robert Raszuk<>  wrote:
>
>>> Independently of that, I think that trying to maintain a session in
>>> the face of multiple errors is a clear waste of time and effort on
>>> all parties.  At some point, there is more effort and complexity
>>> spent on error recovery than on correct transmission, and that's just
>>> backwards.  I support the suggestion of binary exponential back off
>>> on session restarts.
>>>
>>> Regards, Tony
>>
>> I would highly agree that the notion to keep the session at all cost
>> is just a wrong thing to do.
>>
>> Such notion comes often from the fact that operator did not provided
>> path redundancy or are trigger by seemingly correct observation that
>> single malformed update should not impact other correct updates
>> received over the same session.
>>
>> However neither the error handling IDR spec nor it's early
>> implementations provide a way to still allow the reset to happen if X
>> % of UPDATE messages in the window of time T sec are malformed.
>>
>> Perhaps Rob's document as set of requirements could add such
>> requirement to the spec ?
>>
>> Regards,
>> R.
>


From jakob.heitz@ericsson.com  Sun Apr 15 20:40:20 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7FE21F881C for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.333
X-Spam-Level: 
X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHT0w3djCGId for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:40:20 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id D672421F8814 for <grow@ietf.org>; Sun, 15 Apr 2012 20:40:19 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3G3eHW3026254; Sun, 15 Apr 2012 22:40:19 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.157]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Sun, 15 Apr 2012 23:40:11 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Sun, 15 Apr 2012 23:40:10 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0bgdxGksMz8HadTXGebjXvjNPTgwAAEjoA
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA5@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net>
In-Reply-To: <4F8B9314.9030700@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:40:20 -0000

Your algorithm has an error.
You forgot to reset the counter after resetting the session.
How will you handle that error?

Software is not that easy.
Get my point?

On Sunday, April 15, 2012 8:34 PM, Robert Raszuk <mailto:robert@raszuk.net>=
 wrote:

> Hi Jakob,
>=20
> Just to make sure you got my point ...
>=20
> I am not suggesting adding ton of logic and algorithmic operations.
>=20
> All I am suggesting is simple counter (time drained) which would count
> how many times in a given period we are performing the
> treat-as-withdraw=20
> action.
>=20
> Algorithm:
> ----------
>=20
> If such counter get's exceeded session get's reset.
>=20
> There is tracking (counter++ operation) and one additional conditional
> if statement. There is no analysis what so ever.
>=20
> Best,
> R.
>=20
>=20
>> IMO
>> 1. Error handling must be simple, lest we have to handle errors
>> of the error handling, ad infinitum...
>>=20
>> 2. Error handling should be restricted to error isolation
>> and reporting. It should refrain from attempting error recovery.
>>=20
>> If an error can be isolated to a set of NLRI, withdraw them.
>> If an error can only be isolated to a session, reset it.
>>=20
>> Tracking and analysing multiple errors to decide on a reset violates
>> point 1.=20
>>=20
>> On Sunday, April 15, 2012 8:07 PM, Robert Raszuk<>  wrote:
>>=20
>>>> Independently of that, I think that trying to maintain a session in
>>>> the face of multiple errors is a clear waste of time and effort on
>>>> all parties.  At some point, there is more effort and complexity
>>>> spent on error recovery than on correct transmission, and that's
>>>> just backwards.  I support the suggestion of binary exponential
>>>> back off on session restarts.=20
>>>>=20
>>>> Regards, Tony
>>>=20
>>> I would highly agree that the notion to keep the session at all
>>> cost is just a wrong thing to do.=20
>>>=20
>>> Such notion comes often from the fact that operator did not provided
>>> path redundancy or are trigger by seemingly correct observation that
>>> single malformed update should not impact other correct updates
>>> received over the same session.
>>>=20
>>> However neither the error handling IDR spec nor it's early
>>> implementations provide a way to still allow the reset to happen if
>>> X % of UPDATE messages in the window of time T sec are malformed.
>>>=20
>>> Perhaps Rob's document as set of requirements could add such
>>> requirement to the spec ?=20
>>>=20
>>> Regards,
>>> R.

--=20
Jakob Heitz.=

From tony.li@tony.li  Sun Apr 15 20:43:03 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B4A21F867B for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.125
X-Spam-Level: 
X-Spam-Status: No, score=-102.125 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mm5omHnSZSDx for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:43:03 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1D021F8682 for <grow@ietf.org>; Sun, 15 Apr 2012 20:43:02 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta01.westchester.pa.mail.comcast.net with comcast id yTgY1i0061ap0As51Tj3tk; Mon, 16 Apr 2012 03:43:03 +0000
Received: from sjc-vpn2-1084.cisco.com ([128.107.239.233]) by omta22.westchester.pa.mail.comcast.net with comcast id yTin1i00K52qHCY3iTisNc; Mon, 16 Apr 2012 03:43:01 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
Date: Sun, 15 Apr 2012 20:42:46 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <EAC432E1-DE82-4259-8879-A3A58188407B@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
To: Jakob Heitz <jakob.heitz@ericsson.com>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:43:03 -0000

+1

Tony


On Apr 15, 2012, at 8:22 PM, Jakob Heitz wrote:

> IMO
> 1. Error handling must be simple, lest we have to handle errors
> of the error handling, ad infinitum...
> 
> 2. Error handling should be restricted to error isolation
> and reporting. It should refrain from attempting error recovery.
> 
> If an error can be isolated to a set of NLRI, withdraw them.
> If an error can only be isolated to a session, reset it.
> 
> Tracking and analysing multiple errors to decide on a reset
> violates point 1.
> 
> On Sunday, April 15, 2012 8:07 PM, Robert Raszuk <> wrote:
> 
>>> Independently of that, I think that trying to maintain a session in
>>> the face of multiple errors is a clear waste of time and effort on
>>> all parties.  At some point, there is more effort and complexity
>>> spent on error recovery than on correct transmission, and that's just
>>> backwards.  I support the suggestion of binary exponential back off
>>> on session restarts. 
>>> 
>>> Regards, Tony
>> 
>> I would highly agree that the notion to keep the session at all cost
>> is just a wrong thing to do.
>> 
>> Such notion comes often from the fact that operator did not provided
>> path redundancy or are trigger by seemingly correct observation that
>> single malformed update should not impact other correct updates
>> received over the same session.
>> 
>> However neither the error handling IDR spec nor it's early
>> implementations provide a way to still allow the reset to happen if X
>> % of UPDATE messages in the window of time T sec are malformed.
>> 
>> Perhaps Rob's document as set of requirements could add such
>> requirement to the spec ?
>> 
>> Regards,
>> R.
> 
> -- 
> Jakob Heitz.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From robert@raszuk.net  Sun Apr 15 20:55:37 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2486A21F8883 for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2UIOadAAOJrH for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 20:55:36 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 6DDAA21F8868 for <grow@ietf.org>; Sun, 15 Apr 2012 20:55:36 -0700 (PDT)
Received: (qmail 3098 invoked by uid 399); 16 Apr 2012 03:55:35 -0000
Received: from unknown (HELO ?10.0.1.3?) (pbs:robert@raszuk.net@216.31.254.135) by mail1310.opentransfer.com with ESMTPM; 16 Apr 2012 03:55:35 -0000
X-Originating-IP: 216.31.254.135
Message-ID: <4F8B9837.3060604@raszuk.net>
Date: Mon, 16 Apr 2012 05:55:35 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA5@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA5@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 03:55:37 -0000

> Your algorithm has an error.
> You forgot to reset the counter after resetting the session.
> How will you handle that error?

No it does not. This counter is part of dozen of other per session 
counters and variables which get reset and cleared when session goes 
down. No need to for any specific handling of just this counter.

R.



> Software is not that easy.
> Get my point?
>
> On Sunday, April 15, 2012 8:34 PM, Robert Raszuk<mailto:robert@raszuk.net>  wrote:
>
>> Hi Jakob,
>>
>> Just to make sure you got my point ...
>>
>> I am not suggesting adding ton of logic and algorithmic operations.
>>
>> All I am suggesting is simple counter (time drained) which would count
>> how many times in a given period we are performing the
>> treat-as-withdraw
>> action.
>>
>> Algorithm:
>> ----------
>>
>> If such counter get's exceeded session get's reset.
>>
>> There is tracking (counter++ operation) and one additional conditional
>> if statement. There is no analysis what so ever.
>>
>> Best,
>> R.
>>
>>
>>> IMO
>>> 1. Error handling must be simple, lest we have to handle errors
>>> of the error handling, ad infinitum...
>>>
>>> 2. Error handling should be restricted to error isolation
>>> and reporting. It should refrain from attempting error recovery.
>>>
>>> If an error can be isolated to a set of NLRI, withdraw them.
>>> If an error can only be isolated to a session, reset it.
>>>
>>> Tracking and analysing multiple errors to decide on a reset violates
>>> point 1.
>>>
>>> On Sunday, April 15, 2012 8:07 PM, Robert Raszuk<>   wrote:
>>>
>>>>> Independently of that, I think that trying to maintain a session in
>>>>> the face of multiple errors is a clear waste of time and effort on
>>>>> all parties.  At some point, there is more effort and complexity
>>>>> spent on error recovery than on correct transmission, and that's
>>>>> just backwards.  I support the suggestion of binary exponential
>>>>> back off on session restarts.
>>>>>
>>>>> Regards, Tony
>>>>
>>>> I would highly agree that the notion to keep the session at all
>>>> cost is just a wrong thing to do.
>>>>
>>>> Such notion comes often from the fact that operator did not provided
>>>> path redundancy or are trigger by seemingly correct observation that
>>>> single malformed update should not impact other correct updates
>>>> received over the same session.
>>>>
>>>> However neither the error handling IDR spec nor it's early
>>>> implementations provide a way to still allow the reset to happen if
>>>> X % of UPDATE messages in the window of time T sec are malformed.
>>>>
>>>> Perhaps Rob's document as set of requirements could add such
>>>> requirement to the spec ?
>>>>
>>>> Regards,
>>>> R.
>


From jakob.heitz@ericsson.com  Sun Apr 15 21:00:02 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56AE621F86F6 for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 21:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.339
X-Spam-Level: 
X-Spam-Status: No, score=-6.339 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDSWc9kT6Q3O for <grow@ietfa.amsl.com>; Sun, 15 Apr 2012 21:00:01 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id A375721F8699 for <grow@ietf.org>; Sun, 15 Apr 2012 20:59:53 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q3G3xq4Y002187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 15 Apr 2012 22:59:53 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.157]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Sun, 15 Apr 2012 23:59:52 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Sun, 15 Apr 2012 23:59:49 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0bhM7ilCEn+sPvQw6H7z7+yu0zMgAACibw
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAB6@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA5@EUSAACMS0701.eamcs.ericsson.se> <4F8B9837.3060604@raszuk.net>
In-Reply-To: <4F8B9837.3060604@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 04:00:02 -0000

On Sunday, April 15, 2012 8:56 PM, Robert Raszuk <mailto:robert@raszuk.net>=
 wrote:

>> Your algorithm has an error.
>> You forgot to reset the counter after resetting the session.
>> How will you handle that error?
>=20
> No it does not. This counter is part of dozen of other per session
> counters and variables which get reset and cleared when session goes
> down. No need to for any specific handling of just this counter.

We all say "Oh, I meant to do that" when we find a bug.

>=20
> R.
>=20
>=20
>=20
>> Software is not that easy.
>> Get my point?
>>=20
>> On Sunday, April 15, 2012 8:34 PM, Robert
>> Raszuk<mailto:robert@raszuk.net>  wrote:=20
>>=20
>>> Hi Jakob,
>>>=20
>>> Just to make sure you got my point ...
>>>=20
>>> I am not suggesting adding ton of logic and algorithmic operations.
>>>=20
>>> All I am suggesting is simple counter (time drained) which would
>>> count how many times in a given period we are performing the
>>> treat-as-withdraw action.
>>>=20
>>> Algorithm:
>>> ----------
>>>=20
>>> If such counter get's exceeded session get's reset.
>>>=20
>>> There is tracking (counter++ operation) and one additional
>>> conditional if statement. There is no analysis what so ever.
>>>=20
>>> Best,
>>> R.
>>>=20
>>>=20
>>>> IMO
>>>> 1. Error handling must be simple, lest we have to handle errors
>>>> of the error handling, ad infinitum...
>>>>=20
>>>> 2. Error handling should be restricted to error isolation
>>>> and reporting. It should refrain from attempting error recovery.
>>>>=20
>>>> If an error can be isolated to a set of NLRI, withdraw them.
>>>> If an error can only be isolated to a session, reset it.
>>>>=20
>>>> Tracking and analysing multiple errors to decide on a reset
>>>> violates point 1.=20
>>>>=20
>>>> On Sunday, April 15, 2012 8:07 PM, Robert Raszuk<>   wrote:
>>>>=20
>>>>>> Independently of that, I think that trying to maintain a session
>>>>>> in the face of multiple errors is a clear waste of time and
>>>>>> effort on all parties.  At some point, there is more effort and
>>>>>> complexity spent on error recovery than on correct transmission,
>>>>>> and that's just backwards.  I support the suggestion of binary
>>>>>> exponential back off on session restarts.=20
>>>>>>=20
>>>>>> Regards, Tony
>>>>>=20
>>>>> I would highly agree that the notion to keep the session at all
>>>>> cost is just a wrong thing to do.
>>>>>=20
>>>>> Such notion comes often from the fact that operator did not
>>>>> provided path redundancy or are trigger by seemingly correct
>>>>> observation that single malformed update should not impact other
>>>>> correct updates received over the same session.
>>>>>=20
>>>>> However neither the error handling IDR spec nor it's early
>>>>> implementations provide a way to still allow the reset to happen
>>>>> if X % of UPDATE messages in the window of time T sec are
>>>>> malformed.=20
>>>>>=20
>>>>> Perhaps Rob's document as set of requirements could add such
>>>>> requirement to the spec ?=20
>>>>>=20
>>>>> Regards,
>>>>> R.



--=20
Jakob Heitz.=

From ilya@nobulus.com  Mon Apr 16 00:16:45 2012
Return-Path: <ilya@nobulus.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB6F21F8733 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 00:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wWQo7BXe-cCl for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 00:16:45 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id 528C521F867F for <grow@ietf.org>; Mon, 16 Apr 2012 00:16:42 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id 7F11217438; Mon, 16 Apr 2012 09:16:40 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dPysa3H1Haiu; Mon, 16 Apr 2012 09:16:35 +0200 (CEST)
Received: from HNIVARLAS2 (unknown [IPv6:2001:6f8:892:6f8:c8e4:d8c0:2f2d:547e]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nobulus.com (Postfix) with ESMTPSA id 5032217258; Mon, 16 Apr 2012 09:16:35 +0200 (CEST)
From: "Ilya Varlashkin" <ilya@nobulus.com>
To: <robert@raszuk.net>, "'Jakob Heitz'" <jakob.heitz@ericsson.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>	<71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net>
In-Reply-To: <4F8B9314.9030700@raszuk.net>
Date: Mon, 16 Apr 2012 09:16:34 +0200
Message-ID: <000001cd1ba0$db69be30$923d3a90$@nobulus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJXrzlugOVg6qtuNAbmvt26MG7l5wIWnCX2AiHKhzsCRdGJIQIRzgD8lUNfMKA=
Content-Language: en-gb
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 07:16:46 -0000

Robert,

> -----Original Message-----
> Algorithm:
> ----------
> 
> If such counter get's exceeded session get's reset.
> 
> There is tracking (counter++ operation) and one additional conditional if
> statement. There is no analysis what so ever.
> 

Let's consider following scenario: a router in no-longer-kingdom far-away
sends malformed update that somehow manages to slip through multiple
intermediate routers and comes to me via a peer that sends me few dozen
thousands of other prefixes (everyone has seen this in the wild not too long
ago). I increase "error tracking counter", the far-away router for some
reason sends update again, I increase counter again, at some point I reach
threshold. Clearly, resetting my session with a peer that sends me large
number of "good" prefixes isn't to my advantage, especially that it won't
repair distant router. My personal preference would be to ignore such errors
until kingdom come.

On the other hand, if a session is reset (due to errors per other rules)
there's chance that problems will occur again. Rather than bouncing session
for extended period, I'd prefer such troublesome peers to stay down. We
spoke about this behaviour few times, but I'm not sure if we have reached
consensus.

/iLya


From rjs@rob.sh  Mon Apr 16 01:53:23 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2395A21F8733 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 01:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fantcB-bX+TC for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 01:53:22 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 7A21621F8690 for <grow@ietf.org>; Mon, 16 Apr 2012 01:53:22 -0700 (PDT)
Received: from [217.39.14.12] (helo=[10.10.2.94]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SJhfm-0002lt-Km; Mon, 16 Apr 2012 09:52:34 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
Date: Mon, 16 Apr 2012 09:53:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F02033F4-1335-421D-B04C-6121909A5F10@rob.sh>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>
To: Tony Li <tony.li@tony.li>, Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 08:53:23 -0000

Hi,

Thanks for the feedback.

On 13 Apr 2012, at 21:24, Tony Li wrote:

> This may be a nit, but I think it's important to recall that UPDATE =
messages include withdrawn routes.  These MUST NOT be ignored by the =
receiver.  Doing so will simply result in forwarding loops or black =
holes.
>=20
> Perhaps this should at least be wordsmithed into something like =
'ignore any reachability information in an UPDATE message, while =
processing the withdrawn routes in that same UPDATE message'.

Agreed - I think that this is the only place in the draft where there is =
any reference to ignoring a message, but let me re-review this and take =
your suggestion into account.

> Independently of that, I think that trying to maintain a session in =
the face of multiple errors is a clear waste of time and effort on all =
parties.  At some point, there is more effort and complexity spent on =
error recovery than on correct transmission, and that's just backwards.  =
I support the suggestion of binary exponential back off on session =
restarts.

This was the original intent of the section, to ensure that at some =
point there is a cap on the amount of resource that goes into handling =
these errors.=20

The problem with defining an arbitrary cap of "X errors in N time" (as =
Robert suggested) is that this trips up on some particular scenarios:

- A remote AS in the Internet DFZ re-announces prefixes due to upgrading =
border routers, with some changed attribute - it's likely that all their =
prefixes are learnt within a short time period, and if all of them =
include some semantic error, then transitioning to a down state will =
impact the rest of the prefixes in the DFZ unnecessarily.

- If a PE in an L3VPN environment experiences some event (be it =
configuration change, software upgrade, etc) and as a result propagates =
prefixes which are made invalid by an element of the RR infrastructure, =
then a all prefixes will be readvertised within a relatively short time =
period. Again if this results in transitioning the session to a down =
state on the receiving PE (receiving from the RRs), then this impacts =
all prefixes from other PEs unnecessarily.

In both cases these are lower-impact to the receiving PE if they are =
semantic errors, since the action required is likely to be the =
generation of an UPDATE withdrawing these prefixes. Where automatic =
recovery is put in place by an implementor, really the requirement is to =
cap how much of the receiving speaker's resource is used - hence the =
suggestion in the original mail in this thread.

As I see it, for critical errors, where the hitless restart is the way =
of handling the error, then this is somewhat different due to the =
somewhat heavier impact of the receiving PE, plus the fact that the =
error is much more likely to be localised to the directly peered-with =
speaker, and hence the cap of resource by shutting the session down at =
some point, and then exponentially backing off the re-opening process.

Please let me know if this doesn't sound reasonable, or whether there's =
any assumption I made here that's invalid.

Cheers,
r.=

From rjs@rob.sh  Mon Apr 16 02:05:41 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B8C21F8722 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 02:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level: 
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WzK6PqGvdCQG for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 02:05:40 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id A04DC21F8713 for <grow@ietf.org>; Mon, 16 Apr 2012 02:05:40 -0700 (PDT)
Received: from [217.39.14.12] (helo=[10.10.2.94]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SJhre-0002s4-PK; Mon, 16 Apr 2012 10:04:50 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
Date: Mon, 16 Apr 2012 10:05:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6E7A565-CC8A-46F4-B040-FC198B93A9A3@rob.sh>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>
To: Jakob Heitz <jakob.heitz@ericsson.com>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 09:05:41 -0000

On 16 Apr 2012, at 04:22, Jakob Heitz wrote:

> IMO
> 1. Error handling must be simple, lest we have to handle errors
> of the error handling, ad infinitum...
>=20
> 2. Error handling should be restricted to error isolation
> and reporting. It should refrain from attempting error recovery.
>=20
> If an error can be isolated to a set of NLRI, withdraw them.
> If an error can only be isolated to a session, reset it.
>=20
> Tracking and analysing multiple errors to decide on a reset
> violates point 1.

Hi Jakob,

I agree with this, but would like to clarify something here.

I think that there is a requirement to ensure that we do not overwhelm =
the resources of a particular PE by constant session restarts. If one =
were to implement NOTIFICATION-based G-R, when do you stop trying to G-R =
and instead assume that there is something that is not going to go away =
on the other side?

If the answer is "never", then I guess the requirement outlined in the =
section I'm discussing is moot. However, from my POV, there's definitely =
a need to say that at some point my box should stop trying to expend =
effort fixing things (hence the original wording with 'hold up', and now =
the discussion of 'shutdown and back off').

Cheers
r.=

From jakob.heitz@ericsson.com  Mon Apr 16 04:50:54 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B1721F86B4 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 04:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.343
X-Spam-Level: 
X-Spam-Status: No, score=-6.343 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJK9k5OoAGhR for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 04:50:52 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5109E21F86B0 for <grow@ietf.org>; Mon, 16 Apr 2012 04:50:52 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q3GBoo6e015046 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Apr 2012 06:50:51 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.157]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Mon, 16 Apr 2012 07:50:50 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Rob Shakir <rjs@rob.sh>
Date: Mon, 16 Apr 2012 07:50:49 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0bxytcke8ES3cMQ/GI/XCt0kVmRg==
Message-ID: <33789DD3-9A89-4DFF-B1EE-FF2AF98FA08D@ericsson.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <F6E7A565-CC8A-46F4-B040-FC198B93A9A3@rob.sh>
In-Reply-To: <F6E7A565-CC8A-46F4-B040-FC198B93A9A3@rob.sh>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 11:50:54 -0000

This should not overwhelm a router.
However, a more serious consequence is a lot of flapping routes.
Serious enough to consider. We could dust off some dampening code for it.

Note the previous discussion was about repeated "treat as withdraw"
errors. I support the use of an operational message for these errors,
but nothing for repetitions of them. Repeated operational messages
may get annoying, but they are not going to disrupt service.

--
Jakob Heitz.


On Apr 16, 2012, at 2:05 AM, "Rob Shakir" <rjs@rob.sh> wrote:

>=20
> On 16 Apr 2012, at 04:22, Jakob Heitz wrote:
>=20
>> IMO
>> 1. Error handling must be simple, lest we have to handle errors
>> of the error handling, ad infinitum...
>>=20
>> 2. Error handling should be restricted to error isolation
>> and reporting. It should refrain from attempting error recovery.
>>=20
>> If an error can be isolated to a set of NLRI, withdraw them.
>> If an error can only be isolated to a session, reset it.
>>=20
>> Tracking and analysing multiple errors to decide on a reset
>> violates point 1.
>=20
> Hi Jakob,
>=20
> I agree with this, but would like to clarify something here.
>=20
> I think that there is a requirement to ensure that we do not overwhelm th=
e resources of a particular PE by constant session restarts. If one were to=
 implement NOTIFICATION-based G-R, when do you stop trying to G-R and inste=
ad assume that there is something that is not going to go away on the other=
 side?
>=20
> If the answer is "never", then I guess the requirement outlined in the se=
ction I'm discussing is moot. However, from my POV, there's definitely a ne=
ed to say that at some point my box should stop trying to expend effort fix=
ing things (hence the original wording with 'hold up', and now the discussi=
on of 'shutdown and back off').
>=20
> Cheers
> r.

From jared@puck.nether.net  Mon Apr 16 06:35:37 2012
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9938121F8690 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 06:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BoWAZ-krF5jK for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 06:35:37 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0B63621F86C1 for <grow@ietf.org>; Mon, 16 Apr 2012 06:35:36 -0700 (PDT)
Received: from [10.0.0.165] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.5/8.14.4) with ESMTP id q3GDXcnP026131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 16 Apr 2012 09:33:40 -0400
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <33789DD3-9A89-4DFF-B1EE-FF2AF98FA08D@ericsson.com>
Date: Mon, 16 Apr 2012 09:35:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B66288E-5537-4520-946A-91A6204A9884@puck.nether.net>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <F6E7A565-CC8A-46F4-B040-FC198B93A9A3@rob.sh> <33789DD3-9A89-4DFF-B1EE-FF2AF98FA08D@ericsson.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
X-Mailer: Apple Mail (2.1257)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Mon, 16 Apr 2012 09:33:40 -0400 (EDT)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 13:35:37 -0000

On Apr 16, 2012, at 7:50 AM, Jakob Heitz wrote:

> This should not overwhelm a router.
> However, a more serious consequence is a lot of flapping routes.
> Serious enough to consider. We could dust off some dampening code for =
it.
>=20
> Note the previous discussion was about repeated "treat as withdraw"
> errors. I support the use of an operational message for these errors,
> but nothing for repetitions of them. Repeated operational messages
> may get annoying, but they are not going to disrupt service.


The problem we have today is two fold:

1) Vendors have done a bad job of reporting the routes related to a BGP =
session reset
  a - multiple vendor environments can have somewhat catastrophic =
failure modes

2) Stability of the internet (as defined by "keeping the BGP session up =
for the non-broken routes") is important; overall reachability is as =
well.  (to Tony Li's comment about how an update has both feasible and =
infeasible nlri in it).

A broken implementation is just that, broken.  About half the problems =
in the past 24 months are due to improper parsing of a well formed =
update.  With the balance the improper propagation of a invalid update.  =
(I'm willing to be corrected on the exact ratio, but I believe these are =
the two cases seen unless my memory fails me).

I'm hard pressed to imagine a case where the code doesn't quickly get =
unwieldily from this situation.

Part of the requirements of solving this problem will be:

a) Sending an UPDATE message with only new/updated NLRI and zero items =
in the withdrawl.
b) Sending a KEEPALIVE (or other well known message that will be parsed =
properly).
c) Sending an UPDATE message with no new NLRI and only those to be =
withdrawn.

Perhaps this mode is only triggered after a previous session drop within =
3600 seconds.   This means you need to track that state, track a timer, =
and utilize this new (capability?) mode.

We also have a more systematic issue here.  Those participating in the =
global BGP ecosystem need to play an active role in the maintenance of =
these devices.  Failure to do so can and will harm the rest of the =
ecosystem.  I'm not sure the best way to enforce this operationally but =
disabling sessions must be an operational response.  The reason for the =
reset is to *cause pain* for the poorly behaving devices in question and =
draw attention to them.  The same reason a developer would call abort().

The case of dropping the session is the developer equivalent of abort(), =
meant to alert the users to the problem.  Since not everyone running BGP =
is a protocol expert these days, I almost feel we need strict guidance =
and requirements around the logging we need to report these problems to =
the vendors.

- Jared=

From jnc@mercury.lcs.mit.edu  Mon Apr 16 05:40:50 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8BFC21F86DC for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 05:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.185
X-Spam-Level: 
X-Spam-Status: No, score=-5.185 tagged_above=-999 required=5 tests=[AWL=-1.413, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnMR4qmlFVQG for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 05:40:50 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2972421F86D7 for <grow@ietf.org>; Mon, 16 Apr 2012 05:40:50 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5922F18C0D1; Mon, 16 Apr 2012 08:40:49 -0400 (EDT)
To: grow@ietf.org
Message-Id: <20120416124049.5922F18C0D1@mercury.lcs.mit.edu>
Date: Mon, 16 Apr 2012 08:40:49 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailman-Approved-At: Mon, 16 Apr 2012 07:24:42 -0700
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 12:40:50 -0000

    > From: Jakob Heitz <jakob.heitz@ericsson.com>

    > 1. Error handling must be simple, lest we have to handle errors of the
    > error handling, ad infinitum...

    > 2. Error handling should be restricted to error isolation and
    > reporting. It should refrain from attempting error recovery.

I'm going to agree with TLi that these are the basic principles to follow.

In a more advanced architecture (i.e. Map-Distribution based), it might be
possible to do something more advanced in the way of automatic error
analysis/response. However, as things stand, 'ring an alarm bell and have
a human look at it' is about all you can do.

	Noel

From robert@raszuk.net  Mon Apr 16 12:43:39 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5CD11E8099 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 12:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.788
X-Spam-Level: 
X-Spam-Status: No, score=-1.788 tagged_above=-999 required=5 tests=[AWL=0.584,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22p9hxre+6cd for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 12:43:38 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB2211E808C for <grow@ietf.org>; Mon, 16 Apr 2012 12:43:38 -0700 (PDT)
Received: (qmail 30177 invoked by uid 399); 16 Apr 2012 19:43:37 -0000
Received: from unknown (HELO ?216.69.69.171?) (pbs:robert@raszuk.net@216.69.69.171) by mail1310.opentransfer.com with ESMTPM; 16 Apr 2012 19:43:37 -0000
X-Originating-IP: 216.69.69.171
Message-ID: <4F8C7667.2030306@raszuk.net>
Date: Mon, 16 Apr 2012 21:43:35 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Ilya Varlashkin <ilya@nobulus.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>	<71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com>
In-Reply-To: <000001cd1ba0$db69be30$923d3a90$@nobulus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 19:43:39 -0000

Ilya,

I meant to say that you would increment the counter only for unique 
updates. So duplicate updates with the same NLRIs would not be counted N 
times.

 > On the other hand, if a session is reset (due to errors per other
 > rules) there's chance that problems will occur again. Rather than
 > bouncing session for extended period, I'd prefer such troublesome
 > peers to stay down. We spoke about this behaviour few times, but I'm
 > not sure if we have reached consensus.

I agree. We could have max-prefix like configurable restart as an option.

Rgs,
R.

> Robert,
>
>> -----Original Message-----
>> Algorithm:
>> ----------
>>
>> If such counter get's exceeded session get's reset.
>>
>> There is tracking (counter++ operation) and one additional conditional if
>> statement. There is no analysis what so ever.
>>
>
> Let's consider following scenario: a router in no-longer-kingdom far-away
> sends malformed update that somehow manages to slip through multiple
> intermediate routers and comes to me via a peer that sends me few dozen
> thousands of other prefixes (everyone has seen this in the wild not too long
> ago). I increase "error tracking counter", the far-away router for some
> reason sends update again, I increase counter again, at some point I reach
> threshold. Clearly, resetting my session with a peer that sends me large
> number of "good" prefixes isn't to my advantage, especially that it won't
> repair distant router. My personal preference would be to ignore such errors
> until kingdom come.
>
> On the other hand, if a session is reset (due to errors per other rules)
> there's chance that problems will occur again. Rather than bouncing session
> for extended period, I'd prefer such troublesome peers to stay down. We
> spoke about this behaviour few times, but I'm not sure if we have reached
> consensus.
>
> /iLya
>
>
>


From tony.li@tony.li  Mon Apr 16 12:50:10 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B3521F869A for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 12:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.174
X-Spam-Level: 
X-Spam-Status: No, score=-102.174 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DwxDotTzMYx for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 12:50:09 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6BC21F8627 for <grow@ietf.org>; Mon, 16 Apr 2012 12:50:09 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta04.westchester.pa.mail.comcast.net with comcast id ygMu1i00y27AodY54jq9XS; Mon, 16 Apr 2012 19:50:09 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta19.westchester.pa.mail.comcast.net with comcast id yjpu1i01V52qHCY3fjpys6; Mon, 16 Apr 2012 19:50:07 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <4F8C7667.2030306@raszuk.net>
Date: Mon, 16 Apr 2012 12:49:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>	<71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 19:50:10 -0000

So you're going to _remember what error occurred_????

Complexity++

No thanks,
Tony


On Apr 16, 2012, at 12:43 PM, Robert Raszuk wrote:

> Ilya,
>=20
> I meant to say that you would increment the counter only for unique =
updates. So duplicate updates with the same NLRIs would not be counted N =
times.
>=20
> > On the other hand, if a session is reset (due to errors per other
> > rules) there's chance that problems will occur again. Rather than
> > bouncing session for extended period, I'd prefer such troublesome
> > peers to stay down. We spoke about this behaviour few times, but I'm
> > not sure if we have reached consensus.
>=20
> I agree. We could have max-prefix like configurable restart as an =
option.
>=20
> Rgs,
> R.
>=20
>> Robert,
>>=20
>>> -----Original Message-----
>>> Algorithm:
>>> ----------
>>>=20
>>> If such counter get's exceeded session get's reset.
>>>=20
>>> There is tracking (counter++ operation) and one additional =
conditional if
>>> statement. There is no analysis what so ever.
>>>=20
>>=20
>> Let's consider following scenario: a router in no-longer-kingdom =
far-away
>> sends malformed update that somehow manages to slip through multiple
>> intermediate routers and comes to me via a peer that sends me few =
dozen
>> thousands of other prefixes (everyone has seen this in the wild not =
too long
>> ago). I increase "error tracking counter", the far-away router for =
some
>> reason sends update again, I increase counter again, at some point I =
reach
>> threshold. Clearly, resetting my session with a peer that sends me =
large
>> number of "good" prefixes isn't to my advantage, especially that it =
won't
>> repair distant router. My personal preference would be to ignore such =
errors
>> until kingdom come.
>>=20
>> On the other hand, if a session is reset (due to errors per other =
rules)
>> there's chance that problems will occur again. Rather than bouncing =
session
>> for extended period, I'd prefer such troublesome peers to stay down. =
We
>> spoke about this behaviour few times, but I'm not sure if we have =
reached
>> consensus.
>>=20
>> /iLya
>>=20
>>=20
>>=20
>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From robert@raszuk.net  Mon Apr 16 15:01:22 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7303F21F8633 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 15:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.983
X-Spam-Level: 
X-Spam-Status: No, score=-1.983 tagged_above=-999 required=5 tests=[AWL=0.389,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8WICOwpsVHg for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 15:01:22 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id BCED321F862F for <grow@ietf.org>; Mon, 16 Apr 2012 15:01:21 -0700 (PDT)
Received: (qmail 25126 invoked by uid 399); 16 Apr 2012 22:01:21 -0000
Received: from unknown (HELO ?216.69.69.171?) (pbs:m42@mojaklasa.info@216.69.69.171) by mail1310.opentransfer.com with ESMTPM; 16 Apr 2012 22:01:21 -0000
X-Originating-IP: 216.69.69.171
Message-ID: <4F8C96AF.4030602@raszuk.net>
Date: Tue, 17 Apr 2012 00:01:19 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>	<71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li>
In-Reply-To: <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 22:01:22 -0000

Nope.

This is about recognizing duplicate update which good implementation 
should be able to do regardless.

Nothing to do with error itself.

Regards,
R.

> So you're going to _remember what error occurred_????
>
> Complexity++
>
> No thanks,
> Tony
>
>
> On Apr 16, 2012, at 12:43 PM, Robert Raszuk wrote:
>
>> Ilya,
>>
>> I meant to say that you would increment the counter only for unique updates. So duplicate updates with the same NLRIs would not be counted N times.
>>
>>> On the other hand, if a session is reset (due to errors per other
>>> rules) there's chance that problems will occur again. Rather than
>>> bouncing session for extended period, I'd prefer such troublesome
>>> peers to stay down. We spoke about this behaviour few times, but I'm
>>> not sure if we have reached consensus.
>>
>> I agree. We could have max-prefix like configurable restart as an option.
>>
>> Rgs,
>> R.
>>
>>> Robert,
>>>
>>>> -----Original Message-----
>>>> Algorithm:
>>>> ----------
>>>>
>>>> If such counter get's exceeded session get's reset.
>>>>
>>>> There is tracking (counter++ operation) and one additional conditional if
>>>> statement. There is no analysis what so ever.
>>>>
>>>
>>> Let's consider following scenario: a router in no-longer-kingdom far-away
>>> sends malformed update that somehow manages to slip through multiple
>>> intermediate routers and comes to me via a peer that sends me few dozen
>>> thousands of other prefixes (everyone has seen this in the wild not too long
>>> ago). I increase "error tracking counter", the far-away router for some
>>> reason sends update again, I increase counter again, at some point I reach
>>> threshold. Clearly, resetting my session with a peer that sends me large
>>> number of "good" prefixes isn't to my advantage, especially that it won't
>>> repair distant router. My personal preference would be to ignore such errors
>>> until kingdom come.
>>>
>>> On the other hand, if a session is reset (due to errors per other rules)
>>> there's chance that problems will occur again. Rather than bouncing session
>>> for extended period, I'd prefer such troublesome peers to stay down. We
>>> spoke about this behaviour few times, but I'm not sure if we have reached
>>> consensus.
>>>
>>> /iLya
>>>
>>>
>>>
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>
>
>


From christopher.morrow@gmail.com  Mon Apr 16 17:24:30 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABBA311E80EB for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 17:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.486
X-Spam-Level: 
X-Spam-Status: No, score=-103.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0stLYLLM8MJ for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 17:24:30 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id F416311E807F for <grow@ietf.org>; Mon, 16 Apr 2012 17:24:29 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so3357820obb.31 for <grow@ietf.org>; Mon, 16 Apr 2012 17:24:29 -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=NTM2v78mbhLLK0a/dBXu//q2P/i3PpgiMYasYBW9cM8=; b=OKYRx7mZ/S4J27xS682tAuRzQlAfQySrPyN8cj5ne6wUwmbjJEPYvewjwDzgdFndUE JOYyK8n2zE+20lGfqj822R/Hu3CuDi/W4989Ty7tMLqhXqxbpOmP/5s9JF0tvbQYnfqX 25NaBS16aZzvS4kID+b/k+Yu6jFS2ySCLICjeQ4cUUgAO5ADtZBWFP1ImgGpeGrlRFyn lvbdtO0rjtvcELClnJ4wfL6JbEJUEYVu9Wcqz8ag38UacGNk9jd0E2gmdhuL8PzWTsWE 2dvNF1fz2Rbx/hzJB9fJv91BPaCVTfjbqRXWfJRHuE/FV96sMFy0jovyWqshJeS2NXOI wuKA==
MIME-Version: 1.0
Received: by 10.182.52.104 with SMTP id s8mr18326110obo.59.1334622269552; Mon, 16 Apr 2012 17:24:29 -0700 (PDT)
Received: by 10.182.153.34 with HTTP; Mon, 16 Apr 2012 17:24:29 -0700 (PDT)
In-Reply-To: <4F8C96AF.4030602@raszuk.net>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net>
Date: Mon, 16 Apr 2012 20:24:29 -0400
Message-ID: <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: robert@raszuk.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 00:24:30 -0000

On Mon, Apr 16, 2012 at 6:01 PM, Robert Raszuk <robert@raszuk.net> wrote:
> Nope.
>
> This is about recognizing duplicate update which good implementation should
> be able to do regardless.

I think 'good implementations' don't then exist, since ... as
shane/danny have presented a few times, a large percentage of update
traffic seen is repeats from the same speaker.

I'm not sure that being able to track repeats is really necessary
though, if one speaker is +10% bad (pick a percent) over the last 5
mins (or 500 update messages, perhaps this is a chance for a knob for
either/both/mix) shutdown the session and keep it down (or bounce and
re-establish and after X bounces in Y time, shutdown)

If the concern is, this peer keeps sending me an update that is
unparsable, ignoring it (and logging a note/alert/etc) seems ok. If
the problem is that the neighbor did something quite wrong on the
session as a whole more immediate action should be taken.

There's some sympathy to be had for situations like ATTR-128 though,
why bounce 50% of the speakers on the internet repeatedly if some
downstream of a downstream screws up?

-chris

> Nothing to do with error itself.
>
> Regards,
> R.
>
>
>> So you're going to _remember what error occurred_????
>>
>> Complexity++
>>
>> No thanks,
>> Tony
>>
>>
>> On Apr 16, 2012, at 12:43 PM, Robert Raszuk wrote:
>>
>>> Ilya,
>>>
>>> I meant to say that you would increment the counter only for unique
>>> updates. So duplicate updates with the same NLRIs would not be counted N
>>> times.
>>>
>>>> On the other hand, if a session is reset (due to errors per other
>>>> rules) there's chance that problems will occur again. Rather than
>>>> bouncing session for extended period, I'd prefer such troublesome
>>>> peers to stay down. We spoke about this behaviour few times, but I'm
>>>> not sure if we have reached consensus.
>>>
>>>
>>> I agree. We could have max-prefix like configurable restart as an option.
>>>
>>> Rgs,
>>> R.
>>>
>>>> Robert,
>>>>
>>>>> -----Original Message-----
>>>>> Algorithm:
>>>>> ----------
>>>>>
>>>>> If such counter get's exceeded session get's reset.
>>>>>
>>>>> There is tracking (counter++ operation) and one additional conditional
>>>>> if
>>>>> statement. There is no analysis what so ever.
>>>>>
>>>>
>>>> Let's consider following scenario: a router in no-longer-kingdom
>>>> far-away
>>>> sends malformed update that somehow manages to slip through multiple
>>>> intermediate routers and comes to me via a peer that sends me few dozen
>>>> thousands of other prefixes (everyone has seen this in the wild not too
>>>> long
>>>> ago). I increase "error tracking counter", the far-away router for some
>>>> reason sends update again, I increase counter again, at some point I
>>>> reach
>>>> threshold. Clearly, resetting my session with a peer that sends me large
>>>> number of "good" prefixes isn't to my advantage, especially that it
>>>> won't
>>>> repair distant router. My personal preference would be to ignore such
>>>> errors
>>>> until kingdom come.
>>>>
>>>> On the other hand, if a session is reset (due to errors per other rules)
>>>> there's chance that problems will occur again. Rather than bouncing
>>>> session
>>>> for extended period, I'd prefer such troublesome peers to stay down. We
>>>> spoke about this behaviour few times, but I'm not sure if we have
>>>> reached
>>>> consensus.
>>>>
>>>> /iLya
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>>
>>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From tony.li@tony.li  Mon Apr 16 17:37:17 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E23811E80D5 for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 17:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.207
X-Spam-Level: 
X-Spam-Status: No, score=-102.207 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szOptriv+0FX for <grow@ietfa.amsl.com>; Mon, 16 Apr 2012 17:37:16 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by ietfa.amsl.com (Postfix) with ESMTP id A48F411E80D3 for <grow@ietf.org>; Mon, 16 Apr 2012 17:37:16 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta14.westchester.pa.mail.comcast.net with comcast id yoUk1i0051ei1Bg5EodHlB; Tue, 17 Apr 2012 00:37:17 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta24.westchester.pa.mail.comcast.net with comcast id yod41i01Q52qHCY3kod7aN; Tue, 17 Apr 2012 00:37:15 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>
Date: Mon, 16 Apr 2012 17:37:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <230289CF-E514-47A6-9657-19E2B798CA74@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 00:37:17 -0000

On Apr 16, 2012, at 5:24 PM, Christopher Morrow wrote:

> If the concern is, this peer keeps sending me an update that is
> unparsable, ignoring it (and logging a note/alert/etc) seems ok. If
> the problem is that the neighbor did something quite wrong on the
> session as a whole more immediate action should be taken.


Sending something unparsable *is* quite wrong and just ignoring it is =
going to lead to errors down the road.  See previous comment about =
withdrawn routes in updates.

Tony


From ilya@nobulus.com  Tue Apr 17 12:35:30 2012
Return-Path: <ilya@nobulus.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812D111E80D0 for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 12:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T22KjSRYnXBr for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 12:35:30 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id A419911E80CD for <grow@ietf.org>; Tue, 17 Apr 2012 12:35:29 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id 752E417141; Tue, 17 Apr 2012 21:35:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7nYih8AdReZa; Tue, 17 Apr 2012 21:35:23 +0200 (CEST)
Received: from [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684] (unknown [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nobulus.com (Postfix) with ESMTPSA id 332A817122; Tue, 17 Apr 2012 21:35:23 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ilya Varlashkin <ilya@nobulus.com>
In-Reply-To: <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>
Date: Tue, 17 Apr 2012 21:35:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 19:35:30 -0000

On Apr 17, 2012, at 02:24 , Christopher Morrow wrote:

> I'm not sure that being able to track repeats is really necessary
> though, if one speaker is +10% bad (pick a percent) over the last 5
> mins (or 500 update messages, perhaps this is a chance for a knob for
> either/both/mix) shutdown the session and keep it down (or bounce and
> re-establish and after X bounces in Y time, shutdown)
>=20

I'd propose a variation of above:

if number of prefix in "bad update" is higher than configured X% of all =
prefixes (alternatively - 'of best path') learned from this peer =
(regardless of time) then reset session. If X configured to be 100, then =
effectively it means "never drop this session" (unless really all that =
this peer sends is bad).

/iLya=

From robert@raszuk.net  Tue Apr 17 14:00:53 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A7111E80D5 for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tG+OkNoLPC2 for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:00:53 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 1671D11E80D7 for <grow@ietf.org>; Tue, 17 Apr 2012 14:00:53 -0700 (PDT)
Received: (qmail 30211 invoked by uid 399); 17 Apr 2012 21:00:52 -0000
Received: from unknown (HELO ?10.10.246.216?) (pbs:robert@raszuk.net@63.145.238.4) by mail1310.opentransfer.com with ESMTPM; 17 Apr 2012 21:00:52 -0000
X-Originating-IP: 63.145.238.4
Message-ID: <4F8DDA04.8070202@raszuk.net>
Date: Tue, 17 Apr 2012 23:00:52 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Ilya Varlashkin <ilya@nobulus.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com>
In-Reply-To: <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 21:00:53 -0000

Hi Ilya,

I very much agree with your adjustments. My goal was to just provide an 
example of what one could do.

Then to play devil's advocate one could observe that we should perhaps 
not bind the updates to sessions at all. In fact persistence draft is 
just about cutting that binding.

I guess the fact that we use TCP for BGP is sort of legacy and perhaps 
the more Shakespeare we put in BGP (on 179 or different instance) we 
should revisit how we transport the UPDATE messages betwen BGP peers.

Best,
R.


> On Apr 17, 2012, at 02:24 , Christopher Morrow wrote:
>
>> I'm not sure that being able to track repeats is really necessary
>> though, if one speaker is +10% bad (pick a percent) over the last 5
>> mins (or 500 update messages, perhaps this is a chance for a knob for
>> either/both/mix) shutdown the session and keep it down (or bounce and
>> re-establish and after X bounces in Y time, shutdown)
>>
>
> I'd propose a variation of above:
>
> if number of prefix in "bad update" is higher than configured X% of all prefixes (alternatively - 'of best path') learned from this peer (regardless of time) then reset session. If X configured to be 100, then effectively it means "never drop this session" (unless really all that this peer sends is bad).
>
> /iLya
>


From tony.li@tony.li  Tue Apr 17 14:26:33 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5615111E80CE for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.231
X-Spam-Level: 
X-Spam-Status: No, score=-102.231 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDePqgGjMA7H for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:26:33 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id C8BE911E80B2 for <grow@ietf.org>; Tue, 17 Apr 2012 14:26:32 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta05.westchester.pa.mail.comcast.net with comcast id z9JQ1i0041ei1Bg559SZtQ; Tue, 17 Apr 2012 21:26:33 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta24.westchester.pa.mail.comcast.net with comcast id z9SK1i01l52qHCY3k9SPvu; Tue, 17 Apr 2012 21:26:31 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <4F8DDA04.8070202@raszuk.net>
Date: Tue, 17 Apr 2012 14:26:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 21:26:33 -0000

On Apr 17, 2012, at 2:00 PM, Robert Raszuk wrote:

> I guess the fact that we use TCP for BGP is sort of legacy and perhaps =
the more Shakespeare we put in BGP (on 179 or different instance) we =
should revisit how we transport the UPDATE messages betwen BGP peers.


Before you go there, you need to ask yourself if you want to continue to =
have a protocol with incremental updates.  TCP is there precisely to =
support that.

If you want to go back to periodic updates, then getting rid of TCP =
seems much more credible.

But then the overhead become untenable.

Tony


From robert@raszuk.net  Tue Apr 17 14:47:53 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0202511E80A6 for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNJdXAGffuxf for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 14:47:52 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 506D911E8086 for <grow@ietf.org>; Tue, 17 Apr 2012 14:47:52 -0700 (PDT)
Received: (qmail 29696 invoked by uid 399); 17 Apr 2012 21:47:51 -0000
Received: from unknown (HELO ?10.10.246.216?) (pbs:robert@raszuk.net@63.145.238.4) by mail1310.opentransfer.com with ESMTPM; 17 Apr 2012 21:47:51 -0000
X-Originating-IP: 63.145.238.4
Message-ID: <4F8DE507.9030401@raszuk.net>
Date: Tue, 17 Apr 2012 23:47:51 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net> <78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li>
In-Reply-To: <78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 21:47:53 -0000

 > But then the overhead become untenable.

So why not event driven rsync like mechanism between BGP_Adj_Ribs for
incremental updates ? *well for VPNs RTC would need to be mandatory*

Note that RPKI is rsync based which some suggest for BGP to relay on 
anyway ;)

r.


> On Apr 17, 2012, at 2:00 PM, Robert Raszuk wrote:
>
>> I guess the fact that we use TCP for BGP is sort of legacy and
>> perhaps the more Shakespeare we put in BGP (on 179 or different
>> instance) we should revisit how we transport the UPDATE messages
>> betwen BGP peers.
>
> Before you go there, you need to ask yourself if you want to continue
> to have a protocol with incremental updates.  TCP is there precisely
> to support that.
>
> If you want to go back to periodic updates, then getting rid of TCP
> seems much more credible.
>
> But then the overhead become untenable.
>
> Tony
>
>
>


From tony.li@tony.li  Tue Apr 17 15:12:21 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4618721F84AA for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 15:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.248
X-Spam-Level: 
X-Spam-Status: No, score=-102.248 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iP46Rs63GJR for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 15:12:20 -0700 (PDT)
Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by ietfa.amsl.com (Postfix) with ESMTP id D69AE11E8086 for <grow@ietf.org>; Tue, 17 Apr 2012 15:12:20 -0700 (PDT)
Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta02.emeryville.ca.mail.comcast.net with comcast id zA7U1i0050EPchoA2ACLe2; Tue, 17 Apr 2012 22:12:20 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta01.emeryville.ca.mail.comcast.net with comcast id zAC71i00W52qHCY8MAC95n; Tue, 17 Apr 2012 22:12:18 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Tony Li <tony.li@tony.li>
In-Reply-To: <4F8DE507.9030401@raszuk.net>
Date: Tue, 17 Apr 2012 15:12:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net> <78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li> <4F8DE507.9030401@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 22:12:21 -0000

On Apr 17, 2012, at 2:47 PM, Robert Raszuk wrote:

> > But then the overhead become untenable.
>=20
> So why not event driven rsync like mechanism between BGP_Adj_Ribs for
> incremental updates ? *well for VPNs RTC would need to be mandatory*


That doesn't scale particularly well.  The time needed to 'sync' is =
still linear with respect to the number of prefixes, and you end up =
sending a digest of your database. When the items involved gigabit =
files, this is an efficiency win.  When the routes are in the hundreds =
of bytes, you're saving maybe 2 orders of magnitude over the entire =
database. =20

Sure, that's better, but that's a fixed, one time multiplier on scale.  =
Sooner or later, you'll exhaust that.


> Note that RPKI is rsync based which some suggest for BGP to relay on =
anyway ;)


My recollection is that this was for static key information.  Only =
slightly different.  ;-)

Tony



From heas@shrubbery.net  Tue Apr 17 17:47:45 2012
Return-Path: <heas@shrubbery.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9841E21F8496 for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 17:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.372
X-Spam-Level: 
X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9WLcKxdJ5dT for <grow@ietfa.amsl.com>; Tue, 17 Apr 2012 17:47:45 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED27611E8086 for <grow@ietf.org>; Tue, 17 Apr 2012 17:47:44 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 49DE78AF79; Wed, 18 Apr 2012 00:47:44 +0000 (UTC)
Date: Tue, 17 Apr 2012 17:47:44 -0700
From: heasley <heas@shrubbery.net>
To: grow@ietf.org
Message-ID: <20120418004744.GD42205@shrubbery.net>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <230289CF-E514-47A6-9657-19E2B798CA74@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <230289CF-E514-47A6-9657-19E2B798CA74@tony.li>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 00:47:45 -0000

Mon, Apr 16, 2012 at 05:37:02PM -0700, Tony Li:
> 
> On Apr 16, 2012, at 5:24 PM, Christopher Morrow wrote:
> 
> > If the concern is, this peer keeps sending me an update that is
> > unparsable, ignoring it (and logging a note/alert/etc) seems ok. If
> > the problem is that the neighbor did something quite wrong on the
> > session as a whole more immediate action should be taken.
> 
> 
> Sending something unparsable *is* quite wrong and just ignoring it is going to lead to errors down the road.  See previous comment about withdrawn routes in updates.

We agree with Tony.  Furthermore, if an update has a parsing or semantic
error, what degree of confidence does one have that any portion that appears
to be parsable is in fact correct?

Obviously, there is merit in the problem statements, but the assumption that
one could trust any part of a message exhibiting any errors seems like a
rather poor choice.  Without fundamental changes in how updates are handled,
route-refresh seems like the only reliable way short of a reset to ensure
consistency in recovering from a malformed update.

Seems that effort is best directed at improving GR, ISSU, logging (syslog,
more specific notifications & similar) and monitoring capabilities such as
BMP that allow evaluation and tracking on a management host and other tools
that aid in event diagnosis and isolation by operations folk.  Developing
negative testing suites to allow implementors and operators to test response
to bugs that have been seen could also be useful.

From wesley.george@twcable.com  Wed Apr 18 05:41:33 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A837F21F8576 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 05:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.177
X-Spam-Level: 
X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noolmB9t0s5f for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 05:41:30 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC5921F8559 for <grow@ietf.org>; Wed, 18 Apr 2012 05:41:28 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,441,1330923600"; d="scan'208";a="352674160"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 18 Apr 2012 08:40:26 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Wed, 18 Apr 2012 08:41:27 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Tony Li <tony.li@tony.li>, "robert@raszuk.net" <robert@raszuk.net>
Date: Wed, 18 Apr 2012 08:41:27 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0c5ywqxZ2VTyQ5S0e+//9O65lEWgAeJxtg
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173DF7FE52@PRVPEXVS03.corp.twcable.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net>	<000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net>	<F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net>	<78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li> <4F8DE507.9030401@raszuk.net> <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li>
In-Reply-To: <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 12:41:33 -0000

> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of T=
ony
> Li

> > Note that RPKI is rsync based which some suggest for BGP to relay on an=
yway
> ;)
>
>
> My recollection is that this was for static key information.  Only slight=
ly
> different.  ;-)
>

[WEG] That, and as we saw in both IEPG and SIDR, there are a number of pote=
ntial scaling concerns about SIDR's implementation regarding both the amoun=
t of rsync sessions and the method of organizing the repository: http://www=
.ietf.org/mail-archive/web/sidr/current/msg04407.html

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From christopher.morrow@gmail.com  Wed Apr 18 08:10:01 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37A2621F8585 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 08:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-Wj7HkaFtXJ for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 08:09:57 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA49221F856A for <grow@ietf.org>; Wed, 18 Apr 2012 08:09:56 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so6143798obb.31 for <grow@ietf.org>; Wed, 18 Apr 2012 08:09:56 -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:content-transfer-encoding; bh=zwQ2Pc9a5T55F6jwYP28dIeyG7sp8RgN7akwScC6II0=; b=EFdAkglFj3rYSFoQM1E4FmpAuEEF/5vp68MkLf8/8pBLRi4uWEHtoe8jgsD43QERa+ X0QuykV1QEDQ3nGICUdJeJHwFkV5ULZz8sPRM0oNTZO4vWty1pwJKut4sK6g0oc3BdPc zffXShQ/NHwAjHmH2qw7FadAQETRCzcJpEYcnTBOxgl6WXwxdHU/FoIGSWU7CeElxkgO BYnNIZdF0SXmqri4HPX5BqYk9OdHVHZSEMOK6HuGCjvcWqUjH2t/B3lgtAmavNYhRLaC tBRNNMJTZB/rJ8Qa5heDd7z5ocQVOCXkapfmVVNLxpWbgbtq1VeYFdZl1t1TShptLts6 5TSw==
MIME-Version: 1.0
Received: by 10.182.119.74 with SMTP id ks10mr3630476obb.30.1334761796547; Wed, 18 Apr 2012 08:09:56 -0700 (PDT)
Received: by 10.182.22.194 with HTTP; Wed, 18 Apr 2012 08:09:56 -0700 (PDT)
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173DF7FE52@PRVPEXVS03.corp.twcable.com>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net> <78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li> <4F8DE507.9030401@raszuk.net> <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li> <DCC302FAA9FE5F4BBA4DCAD465693779173DF7FE52@PRVPEXVS03.corp.twcable.com>
Date: Wed, 18 Apr 2012 11:09:56 -0400
Message-ID: <CAL9jLaahFbntEJ_7iZTNSeKc1m=RtDqF878qy4ZD2s5=R1bECw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 15:10:01 -0000

On Wed, Apr 18, 2012 at 8:41 AM, George, Wes <wesley.george@twcable.com> wr=
ote:
>
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of =
Tony
>> Li
>
>> > Note that RPKI is rsync based which some suggest for BGP to relay on a=
nyway
>> ;)
>>
>>
>> My recollection is that this was for static key information. =A0Only sli=
ghtly
>> different. =A0;-)
>>
>
> [WEG] That, and as we saw in both IEPG and SIDR, there are a number of po=
tential scaling concerns about SIDR's implementation regarding both the amo=
unt of rsync sessions and the method of organizing the repository: http://w=
ww.ietf.org/mail-archive/web/sidr/current/msg04407.html
>

...neither of which is the 'getting the data to the router' part of
the problem though...

getting data to the router is proposed as just ssh and a bytestream or
some tcp-AO secured stream of bytes (I think).

-chris

From jgs@juniper.net  Wed Apr 18 09:52:30 2012
Return-Path: <jgs@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC4021F8469 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 09:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLaWdv1jsxT4 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 09:52:28 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id CABB321F8466 for <grow@ietf.org>; Wed, 18 Apr 2012 09:52:21 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKT47xRWjoxU1+RXRjO5I9J2TjvTCRZYI/@postini.com; Wed, 18 Apr 2012 09:52:23 PDT
Received: from sa-nc-finance-102.static.jnpr.net (172.23.5.102) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server id 8.3.213.0; Wed, 18 Apr 2012 09:49:18 -0700
MIME-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="us-ascii"
From: "John G. Scudder" <jgs@juniper.net>
In-Reply-To: <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li>
Date: Wed, 18 Apr 2012 09:49:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <22592594-3D75-4532-B6A2-06FA143C310F@juniper.net>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net>	<000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net>	<F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <67DECB2F-2AA8-4CE1-8939-F2A5ECDD6CC4@nobulus.com> <4F8DDA04.8070202@raszuk.net>	<78B4BBCF-6DA7-4752-A382-97AA51DAEAEC@tony.li> <4F8DE507.9030401@raszuk.net> <D012DF7E-F8FA-4F36-A0E8-5138D2059481@tony.li>
To: Tony Li <tony.li@tony.li>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:52:31 -0000

On Apr 17, 2012, at 3:12 PM, Tony Li wrote:

> On Apr 17, 2012, at 2:47 PM, Robert Raszuk wrote:
>=20
>>> But then the overhead become untenable.
>>=20
>> So why not event driven rsync like mechanism between BGP_Adj_Ribs for
>> incremental updates ? *well for VPNs RTC would need to be mandatory*
>=20
>=20
> That doesn't scale particularly well.  The time needed to 'sync' is =
still linear with respect to the number of prefixes, and you end up =
sending a digest of your database. When the items involved gigabit =
files, this is an efficiency win.  When the routes are in the hundreds =
of bytes, you're saving maybe 2 orders of magnitude over the entire =
database. =20
>=20
> Sure, that's better, but that's a fixed, one time multiplier on scale.

Exactly right. Just to add, the cost for the digest isn't just =
transmission, it's also CPU and storage. As you've already pointed out, =
BGP for all its warts doesn't have this particular issue.

--John=

From rbonica@juniper.net  Wed Apr 18 12:20:50 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D386621F84EA for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 12:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.528
X-Spam-Level: 
X-Spam-Status: No, score=-106.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njyDx1hFEjwb for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 12:20:44 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id EBB8D21F84D6 for <grow@ietf.org>; Wed, 18 Apr 2012 12:20:43 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT48UC3uAEbe2/aIuwN1h2alcad8QHJ9K@postini.com; Wed, 18 Apr 2012 12:20:43 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 18 Apr 2012 12:18:44 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 18 Apr 2012 12:18:43 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 18 Apr 2012 15:18:43 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "grow@ietf.org" <grow@ietf.org>
Date: Wed, 18 Apr 2012 15:18:41 -0400
Thread-Topic: draft-ietf-grow-simple-va
Thread-Index: Ac0dmBC5viqaIZVZSjiz8IHC7tTZcg==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A6A8525@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 19:20:50 -0000

Folks,

The WG has recently submitted draft-ietf-grow-simple-va-04 for publication.=
 As part of my AD review, I looked for discussion of this draft on the mail=
ing list. Excluding messages from internet-drafts@ietf.org and the chairs, =
the following are the only messages that I see:

- (Mar-17-2011) http://www.ietf.org/mail-archive/web/grow/current/msg01851.=
html
- (Sep-20-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01748.=
html
- (Aug-23-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01726.=
html
- (Mar-01-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01618.=
html

Given that there has been no discussion of this draft for the last year, an=
d that there was almost no discussion of this draft before that, I need to =
gage the degree to which the WG is still interested in it.

Can anyone speak to the level of WG interest in this draft? As this is an o=
perational WG, I am especially interested in hearing from operators. Howeve=
r, all views are welcomed.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From rbonica@juniper.net  Wed Apr 18 14:31:52 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B3111E80A0 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 14:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.532
X-Spam-Level: 
X-Spam-Status: No, score=-106.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pnnFB9OqrWX for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 14:31:48 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6523111E8095 for <grow@ietf.org>; Wed, 18 Apr 2012 14:31:48 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKT48yxI/IOVDDG1iPuoWK8xTuOkPZz9ej@postini.com; Wed, 18 Apr 2012 14:31:48 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 18 Apr 2012 14:25:47 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 18 Apr 2012 17:25:46 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "grow@ietf.org" <grow@ietf.org>
Date: Wed, 18 Apr 2012 17:25:44 -0400
Thread-Topic: draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2Yw==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 21:31:52 -0000

Folks,

The WG has recently submitted draft-ietf-grow-va-06 for publication. As par=
t of my AD review, I looked for discussion of this draft on the mailing lis=
t archive. Excluding messages from internet-drafts@ietf.org and the chairs,=
 I see no messages posted over the last 12 months. The only messages that I=
 see posted during the previous 12 months are:

- (Mar-17-2011) http://www.ietf.org/mail-archive/web/grow/current/msg01850.=
html
- (Sep-20-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01748.=
html
- (Aug-23-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01726.=
html
- (Jun-23-2010 - Jun-26-2010) IPR Disclosure: Huawei Technologies Co., Ltd'=
s Statement about IPR related to draft-ietf-grow-va-02 and 14 responses

Given this, I need to gage the degree to which the WG is still interested i=
n the draft.

Can anyone speak to the level of WG interest in this draft? As this is an o=
perational WG, I am especially interested in hearing from operators. Howeve=
r, all views are welcomed.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From robert@raszuk.net  Wed Apr 18 14:36:32 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2EA811E8097 for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 14:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwJMTOF4i-0s for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 14:36:28 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 9489D11E8094 for <grow@ietf.org>; Wed, 18 Apr 2012 14:36:28 -0700 (PDT)
Received: (qmail 16212 invoked by uid 399); 18 Apr 2012 21:36:27 -0000
Received: from unknown (HELO ?10.10.246.216?) (pbs:robert@raszuk.net@63.145.238.4) by mail1310.opentransfer.com with ESMTPM; 18 Apr 2012 21:36:27 -0000
X-Originating-IP: 63.145.238.4
Message-ID: <4F8F33DD.6060606@raszuk.net>
Date: Wed, 18 Apr 2012 23:36:29 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8525@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76A6A8525@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 21:36:32 -0000

Hi Ron,

As an author, but also as a current user of this solution I would like 
to support progressing it via IESG.

The draft describes a very simple way to limit number of routing 
messages which get distributed from BGP to RIB and FIBs of the routers.

Moreover it is currently being used in our NTT's network to limit number 
of routes which get set from BGP Route Controller to network forwarding 
elements.

The build in semantic forwarding correctness makes it very safe and 
local control plane to data plane optimization which many carriers, 
ISPs, or enterprises may find very useful to deploy in their networks.

Also both as an co-author as well as operator using it today in the 
working setup I would very welcome comments or suggestions from members 
of this group.

Best regards,
R.


> Folks,
>
> The WG has recently submitted draft-ietf-grow-simple-va-04 for publication. As part of my AD review, I looked for discussion of this draft on the mailing list. Excluding messages from internet-drafts@ietf.org and the chairs, the following are the only messages that I see:
>
> - (Mar-17-2011) http://www.ietf.org/mail-archive/web/grow/current/msg01851.html
> - (Sep-20-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01748.html
> - (Aug-23-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01726.html
> - (Mar-01-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01618.html
>
> Given that there has been no discussion of this draft for the last year, and that there was almost no discussion of this draft before that, I need to gage the degree to which the WG is still interested in it.
>
> Can anyone speak to the level of WG interest in this draft? As this is an operational WG, I am especially interested in hearing from operators. However, all views are welcomed.
>
> --------------------------
> Ron Bonica
> vcard:       www.bonica.org/ron/ronbonica.vcf
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


From shtsuchi@cisco.com  Wed Apr 18 19:37:39 2012
Return-Path: <shtsuchi@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2258211E80AF for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 19:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level: 
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ThJRfXDbpTtZ for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 19:37:32 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 4554411E8089 for <grow@ietf.org>; Wed, 18 Apr 2012 19:37:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=2118; q=dns/txt; s=iport; t=1334803052; x=1336012652; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=36SZZBiSz7v4uRExbDHMoisHnkFNRRdcpXK5ku86epA=; b=b0VyE4N4oqwYr9k/5HV9bbzygsG2o9ovuxrzf/StEKsFX94urYUzvPFp uYt41xGNt07aWpO2zLb79GQ5skKRbaOfeDp/8nRBqzCz/adB5n6/aQlLg C9Djb48wS8iqMUC/itF9KDu8G6Fp62DTYawzarJa2tUjjUjxeMnyvwYn0 c=;
X-IronPort-AV: E=Sophos;i="4.75,445,1330905600"; d="scan'208";a="10385445"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 19 Apr 2012 02:37:30 +0000
Received: from [10.141.32.104] (dhcp-10-141-32-104.cisco.com [10.141.32.104]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3J2bTsE002894; Thu, 19 Apr 2012 02:37:29 GMT
Message-ID: <4F8F7A66.10007@cisco.com>
Date: Thu, 19 Apr 2012 11:37:26 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: rbonica@juniper.net
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8525@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76A6A8525@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, naogawa@cisco.com
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 02:37:39 -0000

Ron
I and my colleague did presentation to the operators group.
APRICOT2012
http://www.apricot2012.net/__data/assets/pdf_file/0019/45523/07-Shishio-Tsuchiya-Simple-Virtual-Aggregation.pdf
JANOG27(Japanese)
http://www.janog.gr.jp/meeting/janog27/doc/janog27-fib-pub-rev00.pdf
We received positive feedback about this feature from some operators.

Today's IPv4 internet route exceeded 400K and IPv6 route has reached 8K.
Of course modern router can support this capacity,but sometimes there is old/poor capacity router in ISP network.
Old/poor router used to be core router,but the router moves to edge router after several years.
In this case,simple-va helps the operators cost.

I support this draft as wg draft.And I hope this draft will publish as RFC as soon as possible.

Regards,
-Shishio

(2012/04/19 4:18), Ronald Bonica wrote:
> Folks,
> 
> The WG has recently submitted draft-ietf-grow-simple-va-04 for publication. As part of my AD review, I looked for discussion of this draft on the mailing list. Excluding messages from internet-drafts@ietf.org and the chairs, the following are the only messages that I see:
> 
> - (Mar-17-2011) http://www.ietf.org/mail-archive/web/grow/current/msg01851.html
> - (Sep-20-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01748.html
> - (Aug-23-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01726.html
> - (Mar-01-2010) http://www.ietf.org/mail-archive/web/grow/current/msg01618.html
> 
> Given that there has been no discussion of this draft for the last year, and that there was almost no discussion of this draft before that, I need to gage the degree to which the WG is still interested in it.
> 
> Can anyone speak to the level of WG interest in this draft? As this is an operational WG, I am especially interested in hearing from operators. However, all views are welcomed.
> 
> --------------------------
> Ron Bonica
> vcard: www.bonica.org/ron/ronbonica.vcf
> 
> 
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 



From tkirkham@anthony-kirkham.com  Wed Apr 18 22:16:21 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172FC21F851B for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 22:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[AWL=1.900,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPLrrrFMUpFG for <grow@ietfa.amsl.com>; Wed, 18 Apr 2012 22:16:17 -0700 (PDT)
Received: from nskntmtas03p.mx.bigpond.com (nskntmtas03p.mx.bigpond.com [61.9.168.143]) by ietfa.amsl.com (Postfix) with ESMTP id D581D21F84E6 for <grow@ietf.org>; Wed, 18 Apr 2012 22:16:16 -0700 (PDT)
Received: from nskntcmgw09p ([61.9.169.169]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20120419051613.CIDH10464.nskntmtas03p.mx.bigpond.com@nskntcmgw09p> for <grow@ietf.org>; Thu, 19 Apr 2012 05:16:13 +0000
Received: from Anthonys-MacBook-Pro.local ([124.187.92.14]) by nskntcmgw09p with BigPond Outbound id zhGB1i00F0JbYsC01hGCpY; Thu, 19 Apr 2012 05:16:13 +0000
X-Authority-Analysis: v=2.0 cv=Lam+G0ji c=1 sm=1 a=eckBsgz14t+FqcypcVY6Mg==:17 a=Vy4kjOWDvb4A:10 a=3cZe9B3ikswA:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=8nJEP1OIZ-IA:10 a=48vgC7mUAAAA:8 a=RehFWjLUiUovX4E7yc0A:9 a=wPNLvfGTeEIA:10 a=lZB815dzVvQA:10 a=eckBsgz14t+FqcypcVY6Mg==:117
Message-ID: <4F8F9F9A.8010609@anthony-kirkham.com>
Date: Thu, 19 Apr 2012 15:16:10 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <20120410064953.27574.88075.idtracker@ietfa.amsl.com>
In-Reply-To: <20120410064953.27574.88075.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 05:16:21 -0000

All,

I'm very keen to know if we can progress this draft to WGLC? Comments 
please?

Tony K


On 10/04/12 4:49 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Global Routing Operations Working Group of the IETF.
>
> 	Title           : Issues with Private IP Addressing in the Internet
> 	Author(s)       : Anthony Kirkham
> 	Filename        : draft-ietf-grow-private-ip-sp-cores-01.txt
> 	Pages           : 15
> 	Date            : 2012-04-09
>
>     The purpose of this document is to provide a discussion of the
>     potential problems of using private, RFC1918, or non-globally-
>     routable addressing within the core of an SP network.  The discussion
>     focuses on link addresses and to a small extent loopback addresses.
>     While many of the issues are well recognised within the ISP
>     community, there appears to be no document that collectively
>     describes the issues.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



From russw@riw.us  Thu Apr 19 19:48:12 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F344621E801A for <grow@ietfa.amsl.com>; Thu, 19 Apr 2012 19:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGLxz-dvT9VY for <grow@ietfa.amsl.com>; Thu, 19 Apr 2012 19:48:11 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id F114C21E800F for <grow@ietf.org>; Thu, 19 Apr 2012 19:47:52 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.119]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1SL3t2-0005Qv-M5 for grow@ietf.org; Thu, 19 Apr 2012 19:47:52 -0700
Message-ID: <4F90CE57.3020004@riw.us>
Date: Thu, 19 Apr 2012 22:47:51 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 02:48:12 -0000

> The WG has recently submitted draft-ietf-grow-va-06 for publication. As part of my AD review, I looked for discussion of this draft on the mailing list archive. Excluding messages from internet-drafts@ietf.org and the chairs, I see no messages posted over the last 12 months. The only messages that I see posted during the previous 12 months are:

IMHO, this isn't one of the "best" ways to go about reducing table size.
Note, however, that I have a "dog in this fight," since Alvaro and I are
working on reviving an older idea that hopes to solve the same sorts of
problems without the complexity of added BGP advertisements.

So --my general feeling is the area of work is interesting, the
mechanism proposed isn't the best available, and I'm ambivalent about
the draft moving forward as an RFC right now.

Russ


From rjs@rob.sh  Fri Apr 20 01:00:43 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37B4121F8777 for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 01:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level: 
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54iD6lXvBlDw for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 01:00:42 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id A175B21F877C for <grow@ietf.org>; Fri, 20 Apr 2012 01:00:42 -0700 (PDT)
Received: from [2001:67c:64:42:5d91:2116:712c:7471] by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SL8ky-00051G-Jg; Fri, 20 Apr 2012 08:59:52 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <20120418004744.GD42205@shrubbery.net>
Date: Fri, 20 Apr 2012 10:00:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <230289CF-E514-47A6-9657-19E2B798CA74@tony.li> <20120418004744.GD42205@shrubbery.net>
To: heasley <heas@shrubbery.net>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 08:00:43 -0000

On 18 Apr 2012, at 02:47, heasley wrote:

> Mon, Apr 16, 2012 at 05:37:02PM -0700, Tony Li:
>>=20
>> On Apr 16, 2012, at 5:24 PM, Christopher Morrow wrote:
>>=20
>>> If the concern is, this peer keeps sending me an update that is
>>> unparsable, ignoring it (and logging a note/alert/etc) seems ok. If
>>> the problem is that the neighbor did something quite wrong on the
>>> session as a whole more immediate action should be taken.
>>=20
>>=20
>> Sending something unparsable *is* quite wrong and just ignoring it is =
going to lead to errors down the road.  See previous comment about =
withdrawn routes in updates.
>=20
> We agree with Tony.  Furthermore, if an update has a parsing or =
semantic
> error, what degree of confidence does one have that any portion that =
appears
> to be parsable is in fact correct?

When the error is with the logic of what is in the well-formed =
attributes, rather than an error with how the UPDATE itself is built, =
then I don't see why this assumption is dangerous. Essentially, where =
treat-as-withdraw is defined as the approach, then the intention is that =
we are confident that we can apply some form of targeted error handling =
to deal with this.=20

A couple of examples off the top of my head:
- AS4_PATH - in this case, we had AS_CONFED_SET in AS4_PATH - the whole =
UPDATE is completely valid just what was in a particular attribute is =
not allowed.
- AS0 in AGGREGATOR =
(http://www.ietf.org/mail-archive/web/idr/current/msg05816.html) - =
again, a valid UPDATE, just where a particular set of content was not =
considered valid.

As I see it, we have to balance the two approaches of absolute =
confidence and correctness against the robustness requirements for how =
the protocol is deployed, and this is what is described in the draft at =
some length. In some deployments the requirement might be for 100% =
correctness, and hence perhaps the requirements described within the =
draft won't be desirable. However, bear in mind that the requirements in =
the draft are not defining that one must deploy all (or even any of) the =
error handling mechanisms in all deployments, but rather it states the =
requirements that occur when one removes the statement that you MUST =
send a NOTIFICATION and hence impact all NLRI. As with all compromises, =
it will be up to individual operators to choose the right balance for =
their deployment.=20

The "semantic" category of errors are those where we consider that we =
can extract the NLRI with a degree of confidence that it is correct. If =
there are problems with the definition in the draft, or the types of =
errors that are listed - let's please discuss this here. I'd really =
welcome as much feedback as possible from the WG on this!

Kind regards,
r.=

From xuxiaohu@huawei.com  Fri Apr 20 00:19:48 2012
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 418EA11E8079 for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 00:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.263
X-Spam-Level: *
X-Spam-Status: No, score=1.263 tagged_above=-999 required=5 tests=[AWL=-0.680,  BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CdJoszbnjaYq for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 00:19:47 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0E93121E802B for <grow@ietf.org>; Fri, 20 Apr 2012 00:19:47 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFJ48137; Fri, 20 Apr 2012 03:19:46 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Apr 2012 00:16:03 -0700
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Apr 2012 00:16:09 -0700
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.28]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Fri, 20 Apr 2012 15:16:04 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Russ White <russw@riw.us>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2YwAsxuKAABnuFMA=
Date: Fri, 20 Apr 2012 07:16:03 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F0E0EF@szxeml525-mbx.china.huawei.com>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net> <4F90CE57.3020004@riw.us>
In-Reply-To: <4F90CE57.3020004@riw.us>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.4.99]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 20 Apr 2012 08:26:21 -0700
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 07:19:48 -0000

DQo+IC0tLS0t08q8/tStvP4tLS0tLQ0KPiC3orz+yMs6IGdyb3ctYm91bmNlc0BpZXRmLm9yZyBb
bWFpbHRvOmdyb3ctYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBSdXNzDQo+IFdoaXRlDQo+ILeiy83K
sbzkOiAyMDEyxOo01MIyMMjVIDEwOjQ4DQo+IMrVvP7IyzogZ3Jvd0BpZXRmLm9yZw0KPiDW98zi
OiBSZTogW0dST1ddIGRyYWZ0LWlldGYtZ3Jvdy12YS0wNg0KPiANCj4gDQo+ID4gVGhlIFdHIGhh
cyByZWNlbnRseSBzdWJtaXR0ZWQgZHJhZnQtaWV0Zi1ncm93LXZhLTA2IGZvciBwdWJsaWNhdGlv
bi4gQXMgcGFydA0KPiBvZiBteSBBRCByZXZpZXcsIEkgbG9va2VkIGZvciBkaXNjdXNzaW9uIG9m
IHRoaXMgZHJhZnQgb24gdGhlIG1haWxpbmcgbGlzdCBhcmNoaXZlLg0KPiBFeGNsdWRpbmcgbWVz
c2FnZXMgZnJvbSBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgYW5kIHRoZSBjaGFpcnMsIEkgc2Vl
IG5vDQo+IG1lc3NhZ2VzIHBvc3RlZCBvdmVyIHRoZSBsYXN0IDEyIG1vbnRocy4gVGhlIG9ubHkg
bWVzc2FnZXMgdGhhdCBJIHNlZSBwb3N0ZWQNCj4gZHVyaW5nIHRoZSBwcmV2aW91cyAxMiBtb250
aHMgYXJlOg0KPiANCj4gSU1ITywgdGhpcyBpc24ndCBvbmUgb2YgdGhlICJiZXN0IiB3YXlzIHRv
IGdvIGFib3V0IHJlZHVjaW5nIHRhYmxlIHNpemUuDQo+IE5vdGUsIGhvd2V2ZXIsIHRoYXQgSSBo
YXZlIGEgImRvZyBpbiB0aGlzIGZpZ2h0LCIgc2luY2UgQWx2YXJvIGFuZCBJIGFyZQ0KPiB3b3Jr
aW5nIG9uIHJldml2aW5nIGFuIG9sZGVyIGlkZWEgdGhhdCBob3BlcyB0byBzb2x2ZSB0aGUgc2Ft
ZSBzb3J0cyBvZg0KPiBwcm9ibGVtcyB3aXRob3V0IHRoZSBjb21wbGV4aXR5IG9mIGFkZGVkIEJH
UCBhZHZlcnRpc2VtZW50cy4NCg0KSGkgUnVzcywNCg0KV291bGQgeW91IGV4cGxhaW4gd2h5IGRv
IHlvdSB0aGluayB0aGUgVkEgbWVjaGFuaXNtIGlzIGNvbXBsZXg/IEJ5IHRoZSB3YXkgLHdvdWxk
IHlvdSBraW5kbHkgZGlzY2xvc2UgYSBiaXQgb2YgZGV0YWlscyBvZiB0aGUgb2xkZXIgaWRlYSB0
aGF0IHlvdSBtZW50aW9uZWQ/IA0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiBTbyAtLW15
IGdlbmVyYWwgZmVlbGluZyBpcyB0aGUgYXJlYSBvZiB3b3JrIGlzIGludGVyZXN0aW5nLCB0aGUN
Cj4gbWVjaGFuaXNtIHByb3Bvc2VkIGlzbid0IHRoZSBiZXN0IGF2YWlsYWJsZSwgYW5kIEknbSBh
bWJpdmFsZW50IGFib3V0DQo+IHRoZSBkcmFmdCBtb3ZpbmcgZm9yd2FyZCBhcyBhbiBSRkMgcmln
aHQgbm93Lg0KPiANCj4gUnVzcw0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gR1JPVyBtYWlsaW5nIGxpc3QNCj4gR1JPV0BpZXRmLm9yZw0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dyb3cNCg==

From tony.li@tony.li  Fri Apr 20 09:27:35 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E3D21F870B for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOAwJu-TuoxO for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:27:35 -0700 (PDT)
Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by ietfa.amsl.com (Postfix) with ESMTP id F17FC21F86DB for <grow@ietf.org>; Fri, 20 Apr 2012 09:27:34 -0700 (PDT)
Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta08.emeryville.ca.mail.comcast.net with comcast id 0GTA1j0040mlR8UA8GTasv; Fri, 20 Apr 2012 16:27:34 +0000
Received: from [10.155.34.251] ([128.107.239.233]) by omta11.emeryville.ca.mail.comcast.net with comcast id 0GTM1j00M52qHCY8XGTPAp; Fri, 20 Apr 2012 16:27:32 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh>
Date: Fri, 20 Apr 2012 09:27:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <47C4A096-BD62-4DE9-A672-0FF0406E71E2@tony.li>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <230289CF-E514-47A6-9657-19E2B798CA74@tony.li> <20120418004744.GD42205@shrubbery.net> <100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh>
To: Rob Shakir <rjs@rob.sh>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 16:27:36 -0000

On Apr 20, 2012, at 1:00 AM, Rob Shakir wrote:

> When the error is with the logic of what is in the well-formed =
attributes, rather than an error with how the UPDATE itself is built, =
then I don't see why this assumption is dangerous. Essentially, where =
treat-as-withdraw is defined as the approach, then the intention is that =
we are confident that we can apply some form of targeted error handling =
to deal with this.=20
>=20
> A couple of examples off the top of my head:
> - AS4_PATH - in this case, we had AS_CONFED_SET in AS4_PATH - the =
whole UPDATE is completely valid just what was in a particular attribute =
is not allowed.
> - AS0 in AGGREGATOR =
(http://www.ietf.org/mail-archive/web/idr/current/msg05816.html) - =
again, a valid UPDATE, just where a particular set of content was not =
considered valid.
>=20
> As I see it, we have to balance the two approaches of absolute =
confidence and correctness against the robustness requirements for how =
the protocol is deployed, and this is what is described in the draft at =
some length. In some deployments the requirement might be for 100% =
correctness, and hence perhaps the requirements described within the =
draft won't be desirable. However, bear in mind that the requirements in =
the draft are not defining that one must deploy all (or even any of) the =
error handling mechanisms in all deployments, but rather it states the =
requirements that occur when one removes the statement that you MUST =
send a NOTIFICATION and hence impact all NLRI. As with all compromises, =
it will be up to individual operators to choose the right balance for =
their deployment.=20
>=20
> The "semantic" category of errors are those where we consider that we =
can extract the NLRI with a degree of confidence that it is correct. If =
there are problems with the definition in the draft, or the types of =
errors that are listed - let's please discuss this here. I'd really =
welcome as much feedback as possible from the WG on this!


Rob,

Thank you, I think that this was enormously constructive.

Yes, if we're willing to dive down a layer, we can classify errors as =
syntactic and semantic.  Syntactic would be ones that include =
inconsistent TLV lengths, unknown mandatory attributes, etc.  Semantic =
errors would be about TLV contents.

I could see taking drastic action for syntactic errors, but being more =
genteel about semantic errors with the exception of NLRI.  If those are =
busted in some way, I don't see how you can even "treat as withdraw".

Regards,
Tony



From jakob.heitz@ericsson.com  Fri Apr 20 09:31:28 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5492721F8643 for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.214
X-Spam-Level: 
X-Spam-Status: No, score=-4.214 tagged_above=-999 required=5 tests=[AWL=-2.157, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBh5atuBRJlj for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:31:19 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7927C21F8639 for <grow@ietf.org>; Fri, 20 Apr 2012 09:31:19 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3KGSot0017940; Fri, 20 Apr 2012 11:28:52 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.157]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Fri, 20 Apr 2012 12:28:46 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, Russ White <russw@riw.us>, "grow@ietf.org" <grow@ietf.org>
Date: Fri, 20 Apr 2012 12:28:45 -0400
Thread-Topic: [GROW] draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2YwAsxuKAABnuFMAAE3s2UA==
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391F08E6262F@EUSAACMS0701.eamcs.ericsson.se>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net> <4F90CE57.3020004@riw.us> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F0E0EF@szxeml525-mbx.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F0E0EF@szxeml525-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 16:31:28 -0000

SXMgdGhlcmUgYSB3YXkgdG8gZG8gTEZBIHdoZW4gdXNpbmcgVkE/DQoNCk9uIEZyaWRheSwgQXBy
aWwgMjAsIDIwMTIgMTI6MTYgQU0sIFh1eGlhb2h1IDw+IHdyb3RlOg0KDQo+PiAtLS0tLdPKvP7U
rbz+LS0tLS0NCj4+ILeivP7IyzogZ3Jvdy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86Z3Jvdy1i
b3VuY2VzQGlldGYub3JnXSC0+rHtIFJ1c3MNCj4+IFdoaXRlDQo+PiC3osvNyrG85DogMjAxMsTq
NNTCMjDI1SAxMDo0OA0KPj4gytW8/sjLOiBncm93QGlldGYub3JnDQo+PiDW98ziOiBSZTogW0dS
T1ddIGRyYWZ0LWlldGYtZ3Jvdy12YS0wNg0KPj4gDQo+PiANCj4+PiBUaGUgV0cgaGFzIHJlY2Vu
dGx5IHN1Ym1pdHRlZCBkcmFmdC1pZXRmLWdyb3ctdmEtMDYgZm9yDQo+Pj4gcHVibGljYXRpb24u
IEFzIHBhcnQgDQo+PiBvZiBteSBBRCByZXZpZXcsIEkgbG9va2VkIGZvciBkaXNjdXNzaW9uIG9m
IHRoaXMgZHJhZnQgb24gdGhlDQo+PiBtYWlsaW5nIGxpc3QgYXJjaGl2ZS4gRXhjbHVkaW5nIG1l
c3NhZ2VzIGZyb20NCj4+IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBhbmQgdGhlIGNoYWlycywg
SSBzZWUgbm8gDQo+PiBtZXNzYWdlcyBwb3N0ZWQgb3ZlciB0aGUgbGFzdCAxMiBtb250aHMuIFRo
ZSBvbmx5IG1lc3NhZ2VzIHRoYXQgSQ0KPj4gc2VlIHBvc3RlZCBkdXJpbmcgdGhlIHByZXZpb3Vz
IDEyIG1vbnRocyBhcmU6DQo+PiANCj4+IElNSE8sIHRoaXMgaXNuJ3Qgb25lIG9mIHRoZSAiYmVz
dCIgd2F5cyB0byBnbyBhYm91dCByZWR1Y2luZyB0YWJsZQ0KPj4gc2l6ZS4gDQo+PiBOb3RlLCBo
b3dldmVyLCB0aGF0IEkgaGF2ZSBhICJkb2cgaW4gdGhpcyBmaWdodCwiIHNpbmNlIEFsdmFybyBh
bmQgSQ0KPj4gYXJlIA0KPj4gd29ya2luZyBvbiByZXZpdmluZyBhbiBvbGRlciBpZGVhIHRoYXQg
aG9wZXMgdG8gc29sdmUgdGhlIHNhbWUgc29ydHMNCj4+IG9mIA0KPj4gcHJvYmxlbXMgd2l0aG91
dCB0aGUgY29tcGxleGl0eSBvZiBhZGRlZCBCR1AgYWR2ZXJ0aXNlbWVudHMuDQo+IA0KPiBIaSBS
dXNzLA0KPiANCj4gV291bGQgeW91IGV4cGxhaW4gd2h5IGRvIHlvdSB0aGluayB0aGUgVkEgbWVj
aGFuaXNtIGlzIGNvbXBsZXg/IEJ5DQo+IHRoZSB3YXkgLHdvdWxkIHlvdSBraW5kbHkgZGlzY2xv
c2UgYSBiaXQgb2YgZGV0YWlscyBvZiB0aGUgb2xkZXIgaWRlYQ0KPiB0aGF0IHlvdSBtZW50aW9u
ZWQ/ICANCj4gDQo+IEJlc3QgcmVnYXJkcywNCj4gWGlhb2h1DQo+IA0KPj4gU28gLS1teSBnZW5l
cmFsIGZlZWxpbmcgaXMgdGhlIGFyZWEgb2Ygd29yayBpcyBpbnRlcmVzdGluZywgdGhlDQo+PiBt
ZWNoYW5pc20gcHJvcG9zZWQgaXNuJ3QgdGhlIGJlc3QgYXZhaWxhYmxlLCBhbmQgSSdtIGFtYml2
YWxlbnQgYWJvdXQNCj4+IHRoZSBkcmFmdCBtb3ZpbmcgZm9yd2FyZCBhcyBhbiBSRkMgcmlnaHQg
bm93Lg0KPj4gDQo+PiBSdXNzDQo+PiANCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+PiBHUk9XIG1haWxpbmcgbGlzdA0KPj4gR1JPV0BpZXRmLm9y
Zw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ncm93DQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEdST1cgbWFpbGlu
ZyBsaXN0DQo+IEdST1dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9ncm93DQoNCi0tIA0KSmFrb2IgSGVpdHou

From robert@raszuk.net  Fri Apr 20 09:43:16 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCE621F8648 for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7InEtxdhFprB for <grow@ietfa.amsl.com>; Fri, 20 Apr 2012 09:43:16 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id DC4BD21F8644 for <grow@ietf.org>; Fri, 20 Apr 2012 09:43:15 -0700 (PDT)
Received: (qmail 22578 invoked by uid 399); 20 Apr 2012 16:43:13 -0000
Received: from unknown (HELO ?192.168.10.87?) (pbs:robert@raszuk.net@208.223.208.242) by mail1310.opentransfer.com with ESMTPM; 20 Apr 2012 16:43:13 -0000
X-Originating-IP: 208.223.208.242
Message-ID: <4F919222.8050703@raszuk.net>
Date: Fri, 20 Apr 2012 18:43:14 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net> <4F90CE57.3020004@riw.us> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F0E0EF@szxeml525-mbx.china.huawei.com> <7309FCBCAE981B43ABBE69B31C8D21391F08E6262F@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391F08E6262F@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Cc: Xuxiaohu <xuxiaohu@huawei.com>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 16:43:16 -0000

Jakob,

LFA operates at the IGP level .. VA operates at the BGP level. I am not
sure what exactly you are asking about.

Thx,
R.

> Is there a way to do LFA when using VA?
> 
> On Friday, April 20, 2012 12:16 AM, Xuxiaohu<>  wrote:
> 
>>> -----ÓÊ¼þÔ­¼þ-----
>>> ·¢¼þÈË: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] ´ú±í Russ
>>> White
>>> ·¢ËÍÊ±¼ä: 2012Äê4ÔÂ20ÈÕ 10:48
>>> ÊÕ¼þÈË: grow@ietf.org
>>> Ö÷Ìâ: Re: [GROW] draft-ietf-grow-va-06
>>>
>>>
>>>> The WG has recently submitted draft-ietf-grow-va-06 for
>>>> publication. As part
>>> of my AD review, I looked for discussion of this draft on the
>>> mailing list archive. Excluding messages from
>>> internet-drafts@ietf.org and the chairs, I see no
>>> messages posted over the last 12 months. The only messages that I
>>> see posted during the previous 12 months are:
>>>
>>> IMHO, this isn't one of the "best" ways to go about reducing table
>>> size.
>>> Note, however, that I have a "dog in this fight," since Alvaro and I
>>> are
>>> working on reviving an older idea that hopes to solve the same sorts
>>> of
>>> problems without the complexity of added BGP advertisements.
>>
>> Hi Russ,
>>
>> Would you explain why do you think the VA mechanism is complex? By
>> the way ,would you kindly disclose a bit of details of the older idea
>> that you mentioned?
>>
>> Best regards,
>> Xiaohu
>>
>>> So --my general feeling is the area of work is interesting, the
>>> mechanism proposed isn't the best available, and I'm ambivalent about
>>> the draft moving forward as an RFC right now.
>>>
>>> Russ
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
> 


From nick@inex.ie  Sun Apr 22 15:05:46 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F073921F8470 for <grow@ietfa.amsl.com>; Sun, 22 Apr 2012 15:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcFpqMrPwN+i for <grow@ietfa.amsl.com>; Sun, 22 Apr 2012 15:05:43 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id B07B921F844E for <grow@ietf.org>; Sun, 22 Apr 2012 15:05:41 -0700 (PDT)
X-Envelope-To: <grow@ietf.org>
Received: from crumpet.foobar.org (twinkie.foobar.org [87.192.56.84]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q3MM5K8c033980 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Sun, 22 Apr 2012 23:05:26 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4F9480AE.9030504@inex.ie>
Date: Sun, 22 Apr 2012 23:05:34 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <20120410064953.27574.88075.idtracker@ietfa.amsl.com> <4F8F9F9A.8010609@anthony-kirkham.com>
In-Reply-To: <4F8F9F9A.8010609@anthony-kirkham.com>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2012 22:05:46 -0000

On 19/04/2012 06:16, Anthony Kirkham wrote:
> All,
> 
> I'm very keen to know if we can progress this draft to WGLC? Comments please?

I like the draft and would like to see it moved to WGLC.  No major
comments, but a couple of nits:

-  weil-shared-transition-space-request is now rfc6598
- the last paragraph in section 5 is sloppily worded.
- section 11, reword "to using private addressing, Such" to be "to using
private addressing; such"
- there are a couple of other incorrect capitalisations and instances of
incorrectly used punctuation marks.

Nick

> Tony K
> 
> 
> On 10/04/12 4:49 PM, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This draft is a work item of the Global Routing Operations
>> Working Group of the IETF.
>>
>>     Title           : Issues with Private IP Addressing in the Internet
>>     Author(s)       : Anthony Kirkham
>>     Filename        : draft-ietf-grow-private-ip-sp-cores-01.txt
>>     Pages           : 15
>>     Date            : 2012-04-09
>>
>>     The purpose of this document is to provide a discussion of the
>>     potential problems of using private, RFC1918, or non-globally-
>>     routable addressing within the core of an SP network.  The discussion
>>     focuses on link addresses and to a small extent loopback addresses.
>>     While many of the issues are well recognised within the ISP
>>     community, there appears to be no document that collectively
>>     describes the issues.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>>
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
> 
> 


-- 
Network Ability Ltd. | Chief Technical Officer | Tel: +353 1 6169698
3 Westland Square    | INEX - Internet Neutral | Fax: +353 1 6041981
Dublin 2, Ireland    | Exchange Association    | Email: nick@inex.ie

From ilya@nobulus.com  Tue Apr 24 00:41:55 2012
Return-Path: <ilya@nobulus.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E753421F85AE for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 00:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level: 
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mr0XpAnfx9Xs for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 00:41:55 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id 40F9D21F853B for <grow@ietf.org>; Tue, 24 Apr 2012 00:41:55 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id D05E917568; Tue, 24 Apr 2012 09:41:53 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JkgQ8t2wf8IY; Tue, 24 Apr 2012 09:41:48 +0200 (CEST)
Received: from HNIVARLAS2 (unknown [IPv6:2001:6f8:892:6f8:396c:4074:3ef1:f70f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nobulus.com (Postfix) with ESMTPSA id 37D6F17544; Tue, 24 Apr 2012 09:41:48 +0200 (CEST)
From: "Ilya Varlashkin" <ilya@nobulus.com>
To: "'Tony Li'" <tony.li@tony.li>, "'Rob Shakir'" <rjs@rob.sh>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>	<4F8B9314.9030700@raszuk.net>	<000001cd1ba0$db69be30$923d3a90$@nobulus.com>	<4F8C7667.2030306@raszuk.net>	<F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li>	<4F8C96AF.4030602@raszuk.net>	<CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>	<230289CF-E514-47A6-9657-19E2B798CA74@tony.li>	<20120418004744.GD42205@shrubbery.net>	<100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh> <47C4A096-BD62-4DE9-A672-0FF0406E71E2@tony.li>
In-Reply-To: <47C4A096-BD62-4DE9-A672-0FF0406E71E2@tony.li>
Date: Tue, 24 Apr 2012 09:41:47 +0200
Message-ID: <00c001cd21ed$b4756290$1d6027b0$@nobulus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIWnCX2W2GiNDqGw11wICiZzCi1XgIhyoc7AkXRiSECEc4A/AIw2ZZ1AptElpoByYAO5wHbPNEvAl+fNekCWzAxKgGdLS/WAciTlykBkOV4nJVRxCGA
Content-Language: en-gb
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 07:41:56 -0000

Hi Toni,

> -----Original Message-----
> Yes, if we're willing to dive down a layer, we can classify errors as
syntactic
> and semantic.  Syntactic would be ones that include inconsistent TLV
lengths,
> unknown mandatory attributes, etc.  Semantic errors would be about TLV
> contents.
> 

How would you classify properly formed TLV out of context? E.g. an attribute
specific to L3VPN attached to a prefix received on a session that supposed
to carry only AFI/SAFI 1/1 - such things did happen in the wild not too long
ago.

/iLya



From jakob.heitz@ericsson.com  Tue Apr 24 00:55:00 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F14CD21F86B4 for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 00:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.892
X-Spam-Level: 
X-Spam-Status: No, score=-5.892 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aP3-qJgSnXcy for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 00:54:59 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD8B21F86B2 for <grow@ietf.org>; Tue, 24 Apr 2012 00:54:59 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3O7suoY008082; Tue, 24 Apr 2012 02:54:57 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 24 Apr 2012 03:54:51 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Ilya Varlashkin <ilya@nobulus.com>
Date: Tue, 24 Apr 2012 03:55:03 -0400
Thread-Topic: [GROW] Repeated Errors in BGP	- draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0h74bkHtlKv1egSqm4S90F8zF4fg==
Message-ID: <0373E992-0928-4137-A2A7-2BDFAD46A344@ericsson.com>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li> <4F8B8CC5.9000906@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se> <4F8B9314.9030700@raszuk.net> <000001cd1ba0$db69be30$923d3a90$@nobulus.com> <4F8C7667.2030306@raszuk.net> <F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li> <4F8C96AF.4030602@raszuk.net> <CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com> <230289CF-E514-47A6-9657-19E2B798CA74@tony.li> <20120418004744.GD42205@shrubbery.net> <100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh> <47C4A096-BD62-4DE9-A672-0FF0406E71E2@tony.li> <00c001cd21ed$b4756290$1d6027b0$@nobulus.com>
In-Reply-To: <00c001cd21ed$b4756290$1d6027b0$@nobulus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP	-	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 07:55:01 -0000

What matters is what to do about it.
Again:
If you can isolate it to a set of NLRI, withdraw them
(and log an error and send an operational message once that becomes availab=
le)
Else reset the session.

The goal is to isolate and report the error, not to recover from the error.

--
Jakob Heitz.


On Apr 24, 2012, at 12:42 AM, "Ilya Varlashkin" <ilya@nobulus.com> wrote:

> Hi Toni,
>=20
>> -----Original Message-----
>> Yes, if we're willing to dive down a layer, we can classify errors as
> syntactic
>> and semantic.  Syntactic would be ones that include inconsistent TLV
> lengths,
>> unknown mandatory attributes, etc.  Semantic errors would be about TLV
>> contents.
>>=20
>=20
> How would you classify properly formed TLV out of context? E.g. an attrib=
ute
> specific to L3VPN attached to a prefix received on a session that suppose=
d
> to carry only AFI/SAFI 1/1 - such things did happen in the wild not too l=
ong
> ago.
>=20
> /iLya
>=20
>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From tony.li@tony.li  Tue Apr 24 08:05:34 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C41D21F8851 for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 08:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.772
X-Spam-Level: 
X-Spam-Status: No, score=-101.772 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6VooPtacghv for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 08:05:33 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC8A21F8850 for <grow@ietf.org>; Tue, 24 Apr 2012 08:05:33 -0700 (PDT)
Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta01.emeryville.ca.mail.comcast.net with comcast id 1qyC1j0090mlR8UA1r5Z3S; Tue, 24 Apr 2012 15:05:33 +0000
Received: from [192.168.2.101] ([98.248.36.188]) by omta11.emeryville.ca.mail.comcast.net with comcast id 1r5V1j00143ZcXW8Xr5XHl; Tue, 24 Apr 2012 15:05:33 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <00c001cd21ed$b4756290$1d6027b0$@nobulus.com>
Date: Tue, 24 Apr 2012 08:05:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B42EBEE-1AFD-42CE-BC7E-24D0BBAC2474@tony.li>
References: <71B128FF-0C61-4D62-A2E2-3DCA6322C3F8@tony.li>	<4F8B8CC5.9000906@raszuk.net>	<7309FCBCAE981B43ABBE69B31C8D21391F08A7DAA1@EUSAACMS0701.eamcs.ericsson.se>	<4F8B9314.9030700@raszuk.net>	<000001cd1ba0$db69be30$923d3a90$@nobulus.com>	<4F8C7667.2030306@raszuk.net>	<F5952E75-E712-4B41-80A0-089204FD0AF9@tony.li>	<4F8C96AF.4030602@raszuk.net>	<CAL9jLaaBhH8mScOa2wA+UspHiQG6_W646nS8DoqToaK+G1aO7A@mail.gmail.com>	<230289CF-E514-47A6-9657-19E2B798CA74@tony.li>	<20120418004744.GD42205@shrubbery.net>	<100755E2-23DA-4BEA-A87F-46BF24F06EED@rob.sh> <47C4A096-BD62-4DE9-A672-0FF0406E71E2@tony.li> <00c001cd21ed$b4756290$1d6027b0$@nobulus.com>
To: "Ilya Varlashkin" <ilya@nobulus.com>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 15:05:34 -0000

On Apr 24, 2012, at 12:41 AM, Ilya Varlashkin wrote:

> How would you classify properly formed TLV out of context? E.g. an =
attribute
> specific to L3VPN attached to a prefix received on a session that =
supposed
> to carry only AFI/SAFI 1/1 - such things did happen in the wild not =
too long
> ago.


Syntactic errors would imply that things are structurally malformed: =
inconsistent lengths in TLVs, for example.  Something that's "properly =
formed" is probably going to always be syntactically correct, so I would =
expect that this would fall into the semantically incorrect bucket.

Tony


From internet-drafts@ietf.org  Tue Apr 24 18:22:39 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E21421F8687; Tue, 24 Apr 2012 18:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8+PrHsIaXbrH; Tue, 24 Apr 2012 18:22:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EA421F8680; Tue, 24 Apr 2012 18:22:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.01p1
Message-ID: <20120425012238.29121.98974.idtracker@ietfa.amsl.com>
Date: Tue, 24 Apr 2012 18:22:38 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-02.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2012 01:22:39 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Issues with Private IP Addressing in the Internet
	Author(s)       : Anthony Kirkham
	Filename        : draft-ietf-grow-private-ip-sp-cores-02.txt
	Pages           : 15
	Date            : 2012-04-24

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-02.=
txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-02.t=
xt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/


From tkirkham@anthony-kirkham.com  Tue Apr 24 18:38:50 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4352121F85DB for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 18:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=0.950,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSfVlhVvGJ7e for <grow@ietfa.amsl.com>; Tue, 24 Apr 2012 18:38:49 -0700 (PDT)
Received: from nschwmtas05p.mx.bigpond.com (nschwmtas05p.mx.bigpond.com [61.9.189.149]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2F421F85D4 for <grow@ietf.org>; Tue, 24 Apr 2012 18:38:49 -0700 (PDT)
Received: from nschwcmgw06p ([61.9.190.166]) by nschwmtas05p.mx.bigpond.com with ESMTP id <20120425013847.NQOU2821.nschwmtas05p.mx.bigpond.com@nschwcmgw06p>;  Wed, 25 Apr 2012 01:38:47 +0000
Received: from Anthonys-MacBook-Pro.local ([124.187.92.14]) by nschwcmgw06p with BigPond Outbound id 21ej1j00G0JbYsC011emUC; Wed, 25 Apr 2012 01:38:47 +0000
X-Authority-Analysis: v=2.0 cv=IpCcgcDg c=1 sm=1 a=eckBsgz14t+FqcypcVY6Mg==:17 a=Vy4kjOWDvb4A:10 a=3cZe9B3ikswA:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=kj9zAlcOel0A:10 a=48vgC7mUAAAA:8 a=VRRTJ5-aRumYiWxeoY8A:9 a=SCwkN3TfgxjS-YOetEsA:7 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=eckBsgz14t+FqcypcVY6Mg==:117
Message-ID: <4F9755A3.3090004@anthony-kirkham.com>
Date: Wed, 25 Apr 2012 11:38:43 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <20120410064953.27574.88075.idtracker@ietfa.amsl.com> <4F8F9F9A.8010609@anthony-kirkham.com> <4F9480AE.9030504@inex.ie>
In-Reply-To: <4F9480AE.9030504@inex.ie>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2012 01:38:50 -0000

Thanks Nick, I have incorporated all that feedback. I re-read it and 
fixed a few other instances of poor capitalisation. If there are any 
other nits, please let me know.

The only other issue I can see is an erroneous index which gets created 
by the XML conversion tool. If anyone has any thoughts on how to change 
or remove it, I'd appreciate the advice.

Tony K



On 23/04/12 8:05 AM, Nick Hilliard wrote:
> On 19/04/2012 06:16, Anthony Kirkham wrote:
>> All,
>>
>> I'm very keen to know if we can progress this draft to WGLC? Comments please?
> I like the draft and would like to see it moved to WGLC.  No major
> comments, but a couple of nits:
>
> -  weil-shared-transition-space-request is now rfc6598
> - the last paragraph in section 5 is sloppily worded.
> - section 11, reword "to using private addressing, Such" to be "to using
> private addressing; such"
> - there are a couple of other incorrect capitalisations and instances of
> incorrectly used punctuation marks.
>
> Nick
>
>> Tony K
>>
>>
>> On 10/04/12 4:49 PM, internet-drafts@ietf.org wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories. This draft is a work item of the Global Routing Operations
>>> Working Group of the IETF.
>>>
>>>      Title           : Issues with Private IP Addressing in the Internet
>>>      Author(s)       : Anthony Kirkham
>>>      Filename        : draft-ietf-grow-private-ip-sp-cores-01.txt
>>>      Pages           : 15
>>>      Date            : 2012-04-09
>>>
>>>      The purpose of this document is to provide a discussion of the
>>>      potential problems of using private, RFC1918, or non-globally-
>>>      routable addressing within the core of an SP network.  The discussion
>>>      focuses on link addresses and to a small extent loopback addresses.
>>>      While many of the issues are well recognised within the ISP
>>>      community, there appears to be no document that collectively
>>>      describes the issues.
>>>
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> This Internet-Draft can be retrieved at:
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
>>>
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>>
>>
>


-- 



From rbonica@juniper.net  Wed Apr 25 16:32:31 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ADC621E8087 for <grow@ietfa.amsl.com>; Wed, 25 Apr 2012 16:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmyhaKxGUhFa for <grow@ietfa.amsl.com>; Wed, 25 Apr 2012 16:32:30 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id AF0F121E8082 for <grow@ietf.org>; Wed, 25 Apr 2012 16:32:30 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT5iJjhZJr6kC3zX6qrCFm6UO2shfnD9r@postini.com; Wed, 25 Apr 2012 16:32:30 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 25 Apr 2012 16:32:18 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 25 Apr 2012 16:32:17 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 25 Apr 2012 19:32:17 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "grow@ietf.org" <grow@ietf.org>
Date: Wed, 25 Apr 2012 19:32:15 -0400
Thread-Topic: draft-ietf-grow-simple-va
Thread-Index: Ac0dmBC5viqaIZVZSjiz8IHC7tTZcgFoTOfg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2012 23:32:31 -0000

Folks,

One week ago, I polled the WG in an attempt to gage interest in draft-ietf-=
grow-simple. The following responses were posted:

- http://www.ietf.org/mail-archive/web/grow/current/msg02228.html
- http://www.ietf.org/mail-archive/web/grow/current/msg02229.html

While these two messages are not sufficient evidence of wide community inte=
rest in this draft, they do suggest that there may be interest out there. S=
o, I will ask the chairs to conduct another WG last call on this draft. In =
the last call announcement, please ask folks who want the draft to be publi=
shed to speak up. Silence will be interpreted as disinterest.

Until the WG last call is complete, I will transition the draft to the AD-W=
ATCHING state.

                                           Ron

> -----Original Message-----
> From: Ronald Bonica
> Sent: Wednesday, April 18, 2012 3:19 PM
> To: grow@ietf.org
> Subject: draft-ietf-grow-simple-va
>=20
> Folks,
>=20
> The WG has recently submitted draft-ietf-grow-simple-va-04 for
> publication. As part of my AD review, I looked for discussion of this
> draft on the mailing list. Excluding messages from internet-
> drafts@ietf.org and the chairs, the following are the only messages
> that I see:
>=20
> - (Mar-17-2011) http://www.ietf.org/mail-
> archive/web/grow/current/msg01851.html
> - (Sep-20-2010) http://www.ietf.org/mail-
> archive/web/grow/current/msg01748.html
> - (Aug-23-2010) http://www.ietf.org/mail-
> archive/web/grow/current/msg01726.html
> - (Mar-01-2010) http://www.ietf.org/mail-
> archive/web/grow/current/msg01618.html
>=20
> Given that there has been no discussion of this draft for the last
> year, and that there was almost no discussion of this draft before
> that, I need to gage the degree to which the WG is still interested in
> it.
>=20
> Can anyone speak to the level of WG interest in this draft? As this is
> an operational WG, I am especially interested in hearing from
> operators. However, all views are welcomed.
>=20
> --------------------------
> Ron Bonica
> vcard:       www.bonica.org/ron/ronbonica.vcf
>=20


From rbonica@juniper.net  Wed Apr 25 16:46:34 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D442621F8638 for <grow@ietfa.amsl.com>; Wed, 25 Apr 2012 16:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60iqywv4oapq for <grow@ietfa.amsl.com>; Wed, 25 Apr 2012 16:46:34 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id F210221F8613 for <grow@ietf.org>; Wed, 25 Apr 2012 16:46:33 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKT5iM2B1ZUcYx0EjtIgBKoZhq6zzy8uox@postini.com; Wed, 25 Apr 2012 16:46:34 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 25 Apr 2012 16:45:06 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 25 Apr 2012 16:45:06 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 25 Apr 2012 19:45:05 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "grow@ietf.org" <grow@ietf.org>
Date: Wed, 25 Apr 2012 19:45:04 -0400
Thread-Topic: draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2YwFkd8VQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AB92C4C@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2012 23:46:34 -0000

Folks,

One week ago, I polled the WG in an attempt to gage interest in draft-ietf-=
grow-va. The following responses were posted:

- http://www.ietf.org/mail-archive/web/grow/current/msg02231.html
- http://www.ietf.org/mail-archive/web/grow/current/msg02233.html
- http://www.ietf.org/mail-archive/web/grow/current/msg02235.html
- http://www.ietf.org/mail-archive/web/grow/current/msg02236.html

I also received one private message referring to an IPR issues surrounding =
the draft.

Of these five messages, two were opposed to publication of the draft, one a=
sked a question, and only two could be interpreted as possibly supporting i=
ts publication. This exchange cannot be interpreted as strong WG support fo=
r publication of the draft.

Therefore, I will transition this draft, and it helper, draft-ietf-grow-va-=
auto to the AD-WATCHING state. If anyone feels that there is strong WG inte=
rest in publishing this draft, they may ask the WG chairs to conduct anothe=
r WG last call o demonstrate interest.

                                             Ron

> -----Original Message-----
> From: Ronald Bonica
> Sent: Wednesday, April 18, 2012 5:26 PM
> To: grow@ietf.org
> Subject: draft-ietf-grow-va-06
>=20
> Folks,
>=20
> The WG has recently submitted draft-ietf-grow-va-06 for publication. As
> part of my AD review, I looked for discussion of this draft on the
> mailing list archive. Excluding messages from internet-drafts@ietf.org
> and the chairs, I see no messages posted over the last 12 months. The
> only messages that I see posted during the previous 12 months are:
>=20
> - (Mar-17-2011) http://www.ietf.org/mail-
> archive/web/grow/current/msg01850.html
> - (Sep-20-2010) http://www.ietf.org/mail-
> archive/web/grow/current/msg01748.html
> - (Aug-23-2010) http://www.ietf.org/mail-
> archive/web/grow/current/msg01726.html
> - (Jun-23-2010 - Jun-26-2010) IPR Disclosure: Huawei Technologies Co.,
> Ltd's Statement about IPR related to draft-ietf-grow-va-02 and 14
> responses
>=20
> Given this, I need to gage the degree to which the WG is still
> interested in the draft.
>=20
> Can anyone speak to the level of WG interest in this draft? As this is
> an operational WG, I am especially interested in hearing from
> operators. However, all views are welcomed.
>=20
> --------------------------
> Ron Bonica
> vcard:       www.bonica.org/ron/ronbonica.vcf
>=20


From rbonica@juniper.net  Fri Apr 27 06:53:15 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5864A21F86B7; Fri, 27 Apr 2012 06:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.552
X-Spam-Level: 
X-Spam-Status: No, score=-106.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVQDMFo90+Kq; Fri, 27 Apr 2012 06:53:14 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 7172C21F865F; Fri, 27 Apr 2012 06:53:06 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKT5qkvKuKtlo9vZeCa4YP/EvvtdFz3qrD@postini.com; Fri, 27 Apr 2012 06:53:14 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 27 Apr 2012 06:51:35 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 27 Apr 2012 06:51:34 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 27 Apr 2012 09:51:22 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "opsawg-chairs@tools.ietf.org" <opsawg-chairs@tools.ietf.org>, "armd-chairs@ietf.org" <armd-chairs@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Date: Fri, 27 Apr 2012 09:51:21 -0400
Thread-Topic: IETF 83 Minutes
Thread-Index: Ac0kfNO+9xVDiYvwS/G8E92BUSSXfw==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AC4423C@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [GROW] IETF 83 Minutes
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Apr 2012 13:53:15 -0000

Folks,

IETF 83 minutes are due today.=20

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From xuxiaohu@huawei.com  Sat Apr 28 00:37:25 2012
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED4821F866C for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 00:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.365
X-Spam-Level: *
X-Spam-Status: No, score=1.365 tagged_above=-999 required=5 tests=[AWL=-0.578,  BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jk9i8-691ZYi for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 00:37:25 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE3321F866A for <grow@ietf.org>; Sat, 28 Apr 2012 00:37:24 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFI91610; Sat, 28 Apr 2012 03:37:24 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 28 Apr 2012 00:36:03 -0700
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 28 Apr 2012 00:36:00 -0700
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.252]) by szxeml418-hub.china.huawei.com ([10.82.67.157]) with mapi id 14.01.0323.003; Sat, 28 Apr 2012 15:35:53 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2YwEGQlEwANL7ZAAAAKi2oA==
Date: Sat, 28 Apr 2012 07:35:53 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F17229@szxeml525-mbx.china.huawei.com>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>  
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.4.99]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Apr 2012 07:37:26 -0000

SGkgUm9uLA0KDQpPbmUgb2YgdGhlIGxhcmdlc3QgU1BzIGluIEV1cm9wZSBoYXMgY29udGFjdGVk
IHVzIGZvciBkb2luZyBhIHRyaWFsIG9uIG91ciBWQSBzb2x1dGlvbiB0d28gbW9udGggYmVmb3Jl
IGFuZCB3ZSBhcmUgbm93IHByZXBhcmluZyBmb3IgdGhhdCB0cmlhbC4gT25jZSB0aGF0IHRyaWFs
IGZpbmlzaGVkLCBtYXliZSB3ZSBjYW4gZXZlbiBzdWJtaXQgYSBleHBlcmltZW50IHJlcG9ydCB0
b2dldGhlciB3aXRoIHRoYXQgU1AgdG8gR1JPVyBmb3IgZnVydGhlciBkaXNjdXNzaW9uLg0KDQpC
eSB0aGUgd2F5LCBhbHRob3VnaCB0aGUgb3JpZ2luYWwgaW50ZW50aW9uIG9mIFZBIGlzIHRvIGFk
ZHJlc3MgdGhlIEludGVybmV0IHJvdXRpbmcgc2NhbGFiaWxpdHkgaXNzdWUsIHRoZSBtZWNoYW5p
c20gZGVzY3JpYmVkIGluIHRoZSBWQSBkcmFmdHMgY2FuIGJlIGFwcGxpZWQgdG8gc29sdmUgdGhl
IGZvcndhcmRpbmcgdGFibGUgc2NhbGFiaWxpdHkgaXNzdWUgaW4gZGF0YSBjZW50ZXIgbmV0d29y
a3MgYXMgd2VsbC4gT25lIGV4YW1wbGUgaXMgVmlydHVhbCBTdWJuZXQgKGh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LXh1LXZpcnR1YWwtc3VibmV0LTA3KSB3aGljaCByZXVzZXMgdGhl
IEZJQiBzdXBwcmVzc2lvbiBtZWNoYW5pc20gZGVzY3JpYmVkIGluIFZBLWF1dG8gdG8gc2NhbGUg
dGhlIGZvcndhcmRpbmcgdGFibGUgb2YgUEUgcm91dGVycy4gRm9yIG1vcmUgZGV0YWlscywgcGxl
YXNlIHNlZSBTZWN0aW9uIDMuNi4yLiJGSUIgUmVkdWN0aW9uIG9uIFBFIFJvdXRlcnMiIG9mIHRo
YXQgZHJhZnQuDQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IC0tLS0t08q8/tStvP4tLS0t
LQ0KPiC3orz+yMs6IGdyb3ctYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmdyb3ctYm91bmNlc0Bp
ZXRmLm9yZ10gtPqx7SBSb25hbGQNCj4gQm9uaWNhDQo+ILeiy83KsbzkOiAyMDEyxOo01MIxOcjV
IDU6MjYNCj4gytW8/sjLOiBncm93QGlldGYub3JnDQo+INb3zOI6IFtHUk9XXSBkcmFmdC1pZXRm
LWdyb3ctdmEtMDYNCj4gDQo+IEZvbGtzLA0KPiANCj4gVGhlIFdHIGhhcyByZWNlbnRseSBzdWJt
aXR0ZWQgZHJhZnQtaWV0Zi1ncm93LXZhLTA2IGZvciBwdWJsaWNhdGlvbi4gQXMgcGFydCBvZg0K
PiBteSBBRCByZXZpZXcsIEkgbG9va2VkIGZvciBkaXNjdXNzaW9uIG9mIHRoaXMgZHJhZnQgb24g
dGhlIG1haWxpbmcgbGlzdCBhcmNoaXZlLg0KPiBFeGNsdWRpbmcgbWVzc2FnZXMgZnJvbSBpbnRl
cm5ldC1kcmFmdHNAaWV0Zi5vcmcgYW5kIHRoZSBjaGFpcnMsIEkgc2VlIG5vDQo+IG1lc3NhZ2Vz
IHBvc3RlZCBvdmVyIHRoZSBsYXN0IDEyIG1vbnRocy4gVGhlIG9ubHkgbWVzc2FnZXMgdGhhdCBJ
IHNlZSBwb3N0ZWQNCj4gZHVyaW5nIHRoZSBwcmV2aW91cyAxMiBtb250aHMgYXJlOg0KPiANCj4g
LSAoTWFyLTE3LTIwMTEpDQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9n
cm93L2N1cnJlbnQvbXNnMDE4NTAuaHRtbA0KPiAtIChTZXAtMjAtMjAxMCkNCj4gaHR0cDovL3d3
dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2dyb3cvY3VycmVudC9tc2cwMTc0OC5odG1sDQo+
IC0gKEF1Zy0yMy0yMDEwKQ0KPiBodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIv
Z3Jvdy9jdXJyZW50L21zZzAxNzI2Lmh0bWwNCj4gLSAoSnVuLTIzLTIwMTAgLSBKdW4tMjYtMjAx
MCkgSVBSIERpc2Nsb3N1cmU6IEh1YXdlaSBUZWNobm9sb2dpZXMgQ28uLCBMdGQncw0KPiBTdGF0
ZW1lbnQgYWJvdXQgSVBSIHJlbGF0ZWQgdG8gZHJhZnQtaWV0Zi1ncm93LXZhLTAyIGFuZCAxNCBy
ZXNwb25zZXMNCj4gDQo+IEdpdmVuIHRoaXMsIEkgbmVlZCB0byBnYWdlIHRoZSBkZWdyZWUgdG8g
d2hpY2ggdGhlIFdHIGlzIHN0aWxsIGludGVyZXN0ZWQgaW4gdGhlDQo+IGRyYWZ0Lg0KPiANCj4g
Q2FuIGFueW9uZSBzcGVhayB0byB0aGUgbGV2ZWwgb2YgV0cgaW50ZXJlc3QgaW4gdGhpcyBkcmFm
dD8gQXMgdGhpcyBpcyBhbg0KPiBvcGVyYXRpb25hbCBXRywgSSBhbSBlc3BlY2lhbGx5IGludGVy
ZXN0ZWQgaW4gaGVhcmluZyBmcm9tIG9wZXJhdG9ycy4gSG93ZXZlciwNCj4gYWxsIHZpZXdzIGFy
ZSB3ZWxjb21lZC4NCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IFJvbiBCb25p
Y2ENCj4gdmNhcmQ6ICAgICAgIHd3dy5ib25pY2Eub3JnL3Jvbi9yb25ib25pY2EudmNmDQo+IA0K
PiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
R1JPVyBtYWlsaW5nIGxpc3QNCj4gR1JPV0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2dyb3cNCg==

From robert@raszuk.net  Sat Apr 28 03:50:59 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0EC21F8694 for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 03:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfyOKdiOOKUc for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 03:50:59 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id DA84921F85C5 for <grow@ietf.org>; Sat, 28 Apr 2012 03:50:58 -0700 (PDT)
Received: (qmail 3725 invoked by uid 399); 28 Apr 2012 10:50:58 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:m42@mojaklasa.info@83.31.245.221) by mail1310.opentransfer.com with ESMTPM; 28 Apr 2012 10:50:58 -0000
X-Originating-IP: 83.31.245.221
Message-ID: <4F9BCB90.9090000@raszuk.net>
Date: Sat, 28 Apr 2012 12:50:56 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Apr 2012 10:50:59 -0000

Hi,

Actually Xiaohu reminded me what triggered my work in this area.

As we all know Routing Research Group has met for number of years and as 
an outcome produced recommendation document which clearly states that 
before transitioning to loc/id split architecture operational community 
can use some form of aggregation where prefix growth would exceed 
forwarding capacity of deployed devices.

Work on VA and simple-va provides a technology to address that precise 
recommendation.

When IETF issues a RFC this becomes a recommendation for the community 
and not for WG it has been develop under. There is no reason for another 
last call of the set of documents in GROW WG. If there is one we need to 
include much broader community including mid and small operators which 
do not attend IETF as they will mostly benefit from this functionality.

Many of them provided vendor who supports this enhancement in production 
os their requirements. Some of them are in native language and not in 
english.

I recommend proceeding with the documents review by IESG. Otherwise I 
think we need to collect broader discussion when an AD is authorized to 
stop progressing useful and deployed technology. Our main goal in the 
IETF should be focused to serve operators to provide tools for them to 
realize new services. It should not be forum to reflect given vendor's 
internal preferences.

Best regards,
R.

> Folks,
>
> One week ago, I polled the WG in an attempt to gage interest in
> draft-ietf-grow-simple. The following responses were posted:
>
> - http://www.ietf.org/mail-archive/web/grow/current/msg02228.html -
> http://www.ietf.org/mail-archive/web/grow/current/msg02229.html
>
> While these two messages are not sufficient evidence of wide
> community interest in this draft, they do suggest that there may be
> interest out there. So, I will ask the chairs to conduct another WG
> last call on this draft. In the last call announcement, please ask
> folks who want the draft to be published to speak up. Silence will be
> interpreted as disinterest.
>
> Until the WG last call is complete, I will transition the draft to
> the AD-WATCHING state.
>
> Ron

From robert@raszuk.net  Sat Apr 28 16:44:00 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C969821F85B6 for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 16:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qy5kvn2jErlT for <grow@ietfa.amsl.com>; Sat, 28 Apr 2012 16:44:00 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 9177421F853F for <grow@ietf.org>; Sat, 28 Apr 2012 16:43:59 -0700 (PDT)
Received: (qmail 17287 invoked by uid 399); 28 Apr 2012 23:43:56 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:robert@raszuk.net@83.9.9.196) by mail1310.opentransfer.com with ESMTPM; 28 Apr 2012 23:43:56 -0000
X-Originating-IP: 83.9.9.196
Message-ID: <4F9C80BA.9040003@raszuk.net>
Date: Sun, 29 Apr 2012 01:43:54 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net>
In-Reply-To: <4F9BCB90.9090000@raszuk.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Apr 2012 23:44:01 -0000

Hi,

Just to put things in perspective I run a few searches today and wrote a 
little script to see what was the former GROW WG traffic for already 
issued RFCs when AD was Mr. Bonica:

RFC6198 -  5 people active on the list (-WG chairs and AD) - 26 messages
RFC6382 - 17 people active on the list (-WG chairs and AD) - 53 messages
RFC6396 - 12 people active on the list (-WG chairs and AD) - 87 messages
RFC6397 -  4 people active on the list (-WG chairs and AD) - 28 messages
RFC6441 - 13 people active on the list (-WG chairs and AD) - 47 messages

With discussions reg -va and simple-va we have this:

12 people active on the list (-WG chairs and AD) - 77 messages

Then as mentioned below one should consider other working groups like 
RRG or IDR also discussing the drafts in question. Last but not least to 
serve a community better one could get to some effort to google a bit 
and see that juniper-nsp had number of discussions on the very subject 
as well:

29 messages - 
http://markmail.org/message/wno3b62wv4j7m74e#query:+page:1+mid:vwb3rnzvfo4dawxi+state:results
j-nsp - [j-nsp] Summarize Global Table - 29 messages
Oct 25 - Oct 28 2011

9 messages - [j-nsp] full table ? 20 sep - oct 12 2011

17 messages on IDR -  draft on virtual aggregation Jul 2008 -
http://www.archivum.info/idr@ietf.org/2008-07/00008/Re-(Idr)-draft-on-virtual-aggregation.html

If those facts and numbers do not provide a sufficient basis to proceed 
with the -va and simple-va documents I do not know what does. If we 
think that we should move the discussion to ietf-interest or similar 
bigger alias to discuss what community support for a given work in IETF 
really means I will be happy to do that.

Best regards,
R.


> Hi,
>
> Actually Xiaohu reminded me what triggered my work in this area.
>
> As we all know Routing Research Group has met for number of years and as
> an outcome produced recommendation document which clearly states that
> before transitioning to loc/id split architecture operational community
> can use some form of aggregation where prefix growth would exceed
> forwarding capacity of deployed devices.
>
> Work on VA and simple-va provides a technology to address that precise
> recommendation.
>
> When IETF issues a RFC this becomes a recommendation for the community
> and not for WG it has been develop under. There is no reason for another
> last call of the set of documents in GROW WG. If there is one we need to
> include much broader community including mid and small operators which
> do not attend IETF as they will mostly benefit from this functionality.
>
> Many of them provided vendor who supports this enhancement in production
> os their requirements. Some of them are in native language and not in
> english.
>
> I recommend proceeding with the documents review by IESG. Otherwise I
> think we need to collect broader discussion when an AD is authorized to
> stop progressing useful and deployed technology. Our main goal in the
> IETF should be focused to serve operators to provide tools for them to
> realize new services. It should not be forum to reflect given vendor's
> internal preferences.
>
> Best regards,
> R.
>
>> Folks,
>>
>> One week ago, I polled the WG in an attempt to gage interest in
>> draft-ietf-grow-simple. The following responses were posted:
>>
>> - http://www.ietf.org/mail-archive/web/grow/current/msg02228.html -
>> http://www.ietf.org/mail-archive/web/grow/current/msg02229.html
>>
>> While these two messages are not sufficient evidence of wide
>> community interest in this draft, they do suggest that there may be
>> interest out there. So, I will ask the chairs to conduct another WG
>> last call on this draft. In the last call announcement, please ask
>> folks who want the draft to be published to speak up. Silence will be
>> interpreted as disinterest.
>>
>> Until the WG last call is complete, I will transition the draft to
>> the AD-WATCHING state.
>>
>> Ron
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


From rbonica@juniper.net  Sun Apr 29 13:13:44 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F202F21F85C6; Sun, 29 Apr 2012 13:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2bnpnlNMpRr; Sun, 29 Apr 2012 13:13:43 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3713021F85C7; Sun, 29 Apr 2012 13:13:42 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKT52g9R56viCGEvr84cQayKDag1zvGHLM@postini.com; Sun, 29 Apr 2012 13:13:43 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 29 Apr 2012 13:13:41 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Sun, 29 Apr 2012 16:13:40 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "robert@raszuk.net" <robert@raszuk.net>, "grow@ietf.org" <grow@ietf.org>,  "iesg@ietf.org" <iesg@ietf.org>
Date: Sun, 29 Apr 2012 16:13:39 -0400
Thread-Topic: [GROW] draft-ietf-grow-simple-va
Thread-Index: Ac0lmMi09H4F5Uy0ScS65NZjwALcOQAqpovA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net>
In-Reply-To: <4F9C80BA.9040003@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Apr 2012 20:13:44 -0000

If we
> think that we should move the discussion to ietf-interest or similar
> bigger alias to discuss what community support for a given work in IETF
> really means I will be happy to do that.
>=20
> Best regards,
> R.
>=20

Robert,=20

This is a pretty good idea!=20

So, I would ask the chairs to post another WG last call on both documents. =
In the last call, please mention that we are looking to gage community inte=
rest, so silence  will not be interpreted as consent.

Robert, would you be willing to call attention to the last call on whatever=
 mailing lists you think appropriate. The list ietf@ietf.org leaps to mind,=
 but you might think of others, too.

                                                                    Ron


From robert@raszuk.net  Sun Apr 29 13:21:00 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDD221F84EA for <grow@ietfa.amsl.com>; Sun, 29 Apr 2012 13:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhVcG0V-eYvz for <grow@ietfa.amsl.com>; Sun, 29 Apr 2012 13:21:00 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id E5EA421F84D3 for <grow@ietf.org>; Sun, 29 Apr 2012 13:20:59 -0700 (PDT)
Received: (qmail 7406 invoked by uid 399); 29 Apr 2012 20:20:59 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:robert@raszuk.net@83.9.96.100) by mail1310.opentransfer.com with ESMTPM; 29 Apr 2012 20:20:59 -0000
X-Originating-IP: 83.9.96.100
Message-ID: <4F9DA2A9.7070301@raszuk.net>
Date: Sun, 29 Apr 2012 22:20:57 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Apr 2012 20:21:00 -0000

Ronald,

This document as proven in my last email with real number got sufficient
attention already and there is no need for another last call.

Please explain why those documents require more community support then 
other documents issued as RFCs in the GROW WG.

The quote below was to evaluate what others understand by "sufficient
community support".

R.

> If we
>> think that we should move the discussion to ietf-interest or
>> similar bigger alias to discuss what community support for a given
>> work in IETF really means I will be happy to do that.
>>
>> Best regards, R.
>>
>
> Robert,
>
> This is a pretty good idea!
>
> So, I would ask the chairs to post another WG last call on both
> documents. In the last call, please mention that we are looking to
> gage community interest, so silence  will not be interpreted as
> consent.
>
> Robert, would you be willing to call attention to the last call on
> whatever mailing lists you think appropriate. The list ietf@ietf.org
> leaps to mind, but you might think of others, too.
>
> Ron
>
>
>


From rbonica@juniper.net  Sun Apr 29 19:43:23 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1719B21F84E6; Sun, 29 Apr 2012 19:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.555
X-Spam-Level: 
X-Spam-Status: No, score=-106.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkaFeBgSL23Y; Sun, 29 Apr 2012 19:43:22 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 442E921F8466; Sun, 29 Apr 2012 19:43:21 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKT538SN5BX1a+vgS/uEWUi/dfkW7SKaFG@postini.com; Sun, 29 Apr 2012 19:43:22 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 29 Apr 2012 19:42:43 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sun, 29 Apr 2012 22:42:42 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Sun, 29 Apr 2012 22:42:41 -0400
Thread-Topic: [GROW] draft-ietf-grow-simple-va
Thread-Index: Ac0mRZiv+cuHU73uRY6iG7yaAcW1dQAJTYtQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net>
In-Reply-To: <4F9DA2A9.7070301@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 02:43:23 -0000

Robert,

These drafts are unique in my experience as an AD.=20

The WG Last Call appears to have occurred in the 14 days following July 29,=
 2010. I don't see any firm conclusion to that last call. The closest thing=
 to a conclusion that I see is the following message in which Paul Francis =
encourages the chairs to interpret silence as consent:

- http://www.ietf.org/mail-archive/web/grow/current/msg01748.html

However, the chairs are silent. On March 17, 2011, I see the following mess=
ages from Wes George:

- http://www.ietf.org/mail-archive/web/grow/current/msg01851.html
- http://www.ietf.org/mail-archive/web/grow/current/msg01850.html

Because the authors are still seeking review seven months after the WG Last=
 Call, I infer that the July 29 Last Call was inconclusive. (Otherwise, why=
 would they still be seeking review?)

I have no clear indication that consensus was called until March, 2012 when=
 the chairs sent the drafts to me for publication. However, because the WG =
was mostly silent regarding these drafts between March 2011 and March 2012,=
 I have no idea what events caused consensus to be called.

Because the WG Last Call process was so irregular, I asked about WG interes=
t and received a tepid response. As I recall, only one positive response po=
sted by a non-author.

So, how do we proceed? If you want to demonstrate WG support of draft-ietf-=
grow-simple-va, let the WG LC proceed. If you want to publish without demon=
strating WG support, I would be glad to AD sponsor that draft.

However, I have reservations about AD sponsoring draft-ietf-grow-va because=
 of the negative response I received regarding that draft when I queried th=
e mailing list. I would really be much more comfortable if that draft went =
through another IETF last call.

                                    Ron

P.S. BTW, the short answer to your question is that these drafts are receiv=
ing more scrutiny because the WG Last Call process was so irregular.


> -----Original Message-----
> From: Robert Raszuk [mailto:robert@raszuk.net]
> Sent: Sunday, April 29, 2012 4:21 PM
> To: Ronald Bonica
> Cc: grow@ietf.org; iesg@ietf.org
> Subject: Re: [GROW] draft-ietf-grow-simple-va
>=20
> Ronald,
>=20
> This document as proven in my last email with real number got
> sufficient attention already and there is no need for another last
> call.
>=20
> Please explain why those documents require more community support then
> other documents issued as RFCs in the GROW WG.
>=20
> The quote below was to evaluate what others understand by "sufficient
> community support".
>=20
> R.
>=20
> > If we
> >> think that we should move the discussion to ietf-interest or similar
> >> bigger alias to discuss what community support for a given work in
> >> IETF really means I will be happy to do that.
> >>
> >> Best regards, R.
> >>
> >
> > Robert,
> >
> > This is a pretty good idea!
> >
> > So, I would ask the chairs to post another WG last call on both
> > documents. In the last call, please mention that we are looking to
> > gage community interest, so silence  will not be interpreted as
> > consent.
> >
> > Robert, would you be willing to call attention to the last call on
> > whatever mailing lists you think appropriate. The list ietf@ietf.org
> > leaps to mind, but you might think of others, too.
> >
> > Ron
> >
> >
> >


From robert@raszuk.net  Sun Apr 29 22:49:05 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B75A21F8564 for <grow@ietfa.amsl.com>; Sun, 29 Apr 2012 22:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hs9TgBX4bBpf for <grow@ietfa.amsl.com>; Sun, 29 Apr 2012 22:49:04 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB8421F8582 for <grow@ietf.org>; Sun, 29 Apr 2012 22:49:04 -0700 (PDT)
Received: (qmail 9511 invoked by uid 399); 30 Apr 2012 05:49:02 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:m42@mojaklasa.info@83.9.209.45) by mail1310.opentransfer.com with ESMTPM; 30 Apr 2012 05:49:02 -0000
X-Originating-IP: 83.9.209.45
Message-ID: <4F9E27CC.8070507@raszuk.net>
Date: Mon, 30 Apr 2012 07:49:00 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 05:49:05 -0000

Ron,

>> So, how do we proceed? If you want to demonstrate WG support of
 >> draft-ietf-grow-simple-va, let the WG LC proceed. If you want to
 >> publish without demonstrating WG support, I would be glad to AD
>> sponsor that draft.

Please proceed with AD sponsorship on this draft.

In my view the idea and the draft have already received sufficient 
support within this group, other IETF and IRTF groups as well as outside 
of IETF in various public forums.

Thx,
R.

From xuxiaohu@huawei.com  Mon Apr 23 19:53:00 2012
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1382C11E8072 for <grow@ietfa.amsl.com>; Mon, 23 Apr 2012 19:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.348
X-Spam-Level: *
X-Spam-Status: No, score=1.348 tagged_above=-999 required=5 tests=[AWL=-0.595,  BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIPwcOfD9K1a for <grow@ietfa.amsl.com>; Mon, 23 Apr 2012 19:52:58 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 672C921F86D3 for <grow@ietf.org>; Mon, 23 Apr 2012 19:52:51 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFD94986; Mon, 23 Apr 2012 22:52:51 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 23 Apr 2012 19:50:10 -0700
Received: from SZXEML436-HUB.china.huawei.com (10.72.61.64) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 23 Apr 2012 19:50:12 -0700
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.28]) by szxeml436-hub.china.huawei.com ([10.72.61.64]) with mapi id 14.01.0323.003; Tue, 24 Apr 2012 10:50:08 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: draft-ietf-grow-va-06
Thread-Index: Ac0dqdCJqg2iUU35TT+pAy0eB8n2YwEGQlEw
Date: Tue, 24 Apr 2012 02:50:07 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F0EB8D@szxeml525-mbx.china.huawei.com>
References: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76A6A8800@EMBX01-WF.jnpr.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.4.99]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 30 Apr 2012 08:27:16 -0700
Subject: Re: [GROW] draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 02:53:00 -0000

SGkgUm9uLA0KDQpPbmUgb2YgdGhlIGxhcmdlc3QgU1BzIGluIEV1cm9wZSBoYXMgY29udGFjdGVk
IHVzIGZvciBkb2luZyBhIHRyaWFsIG9uIG91ciBWQSBzb2x1dGlvbiB0d28gbW9udGggYmVmb3Jl
IGFuZCB3ZSBhcmUgbm93IHByZXBhcmluZyBmb3IgdGhhdCB0cmlhbC4gT25jZSB0aGF0IHRyaWFs
IGZpbmlzaGVkLCBtYXliZSB3ZSBjYW4gZXZlbiBzdWJtaXQgYSBleHBlcmltZW50IHJlcG9ydCB0
b2dldGhlciB3aXRoIHRoYXQgU1AgdG8gR1JPVyBmb3IgZnVydGhlciBkaXNjdXNzaW9uLg0KDQpC
eSB0aGUgd2F5LCBhbHRob3VnaCB0aGUgb3JpZ2luYWwgaW50ZW50aW9uIG9mIFZBIGlzIHRvIGFk
ZHJlc3MgdGhlIEludGVybmV0IHJvdXRpbmcgc2NhbGFiaWxpdHkgaXNzdWUsIHRoZSBtZWNoYW5p
c20gZGVzY3JpYmVkIGluIHRoZSBWQSBkcmFmdHMgY2FuIGJlIGFwcGxpZWQgdG8gc29sdmUgdGhl
IGZvcndhcmRpbmcgdGFibGUgc2NhbGFiaWxpdHkgaXNzdWUgaW4gZGF0YSBjZW50ZXIgbmV0d29y
a3MgYXMgd2VsbC4gT25lIGV4YW1wbGUgaXMgVmlydHVhbCBTdWJuZXQgKGh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LXh1LXZpcnR1YWwtc3VibmV0LTA3KSB3aGljaCByZXVzZXMgdGhl
IEZJQiBzdXBwcmVzc2lvbiBtZWNoYW5pc20gZGVzY3JpYmVkIGluIFZBIHRvIHNjYWxlIHRoZSBm
b3J3YXJkaW5nIHRhYmxlIG9mIFBFIHJvdXRlcnMuIEZvciBtb3JlIGRldGFpbHMsIHBsZWFzZSBz
ZWUgU2VjdGlvbiAzLjYuMi4iRklCIFJlZHVjdGlvbiBvbiBQRSBSb3V0ZXJzIiBvZiB0aGF0IGRy
YWZ0Lg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4g
t6K8/sjLOiBncm93LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpncm93LWJvdW5jZXNAaWV0Zi5v
cmddILT6se0gUm9uYWxkDQo+IEJvbmljYQ0KPiC3osvNyrG85DogMjAxMsTqNNTCMTnI1SA1OjI2
DQo+IMrVvP7IyzogZ3Jvd0BpZXRmLm9yZw0KPiDW98ziOiBbR1JPV10gZHJhZnQtaWV0Zi1ncm93
LXZhLTA2DQo+IA0KPiBGb2xrcywNCj4gDQo+IFRoZSBXRyBoYXMgcmVjZW50bHkgc3VibWl0dGVk
IGRyYWZ0LWlldGYtZ3Jvdy12YS0wNiBmb3IgcHVibGljYXRpb24uIEFzIHBhcnQgb2YNCj4gbXkg
QUQgcmV2aWV3LCBJIGxvb2tlZCBmb3IgZGlzY3Vzc2lvbiBvZiB0aGlzIGRyYWZ0IG9uIHRoZSBt
YWlsaW5nIGxpc3QgYXJjaGl2ZS4NCj4gRXhjbHVkaW5nIG1lc3NhZ2VzIGZyb20gaW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnIGFuZCB0aGUgY2hhaXJzLCBJIHNlZSBubw0KPiBtZXNzYWdlcyBwb3N0
ZWQgb3ZlciB0aGUgbGFzdCAxMiBtb250aHMuIFRoZSBvbmx5IG1lc3NhZ2VzIHRoYXQgSSBzZWUg
cG9zdGVkDQo+IGR1cmluZyB0aGUgcHJldmlvdXMgMTIgbW9udGhzIGFyZToNCj4gDQo+IC0gKE1h
ci0xNy0yMDExKQ0KPiBodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvZ3Jvdy9j
dXJyZW50L21zZzAxODUwLmh0bWwNCj4gLSAoU2VwLTIwLTIwMTApDQo+IGh0dHA6Ly93d3cuaWV0
Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9ncm93L2N1cnJlbnQvbXNnMDE3NDguaHRtbA0KPiAtIChB
dWctMjMtMjAxMCkNCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2dyb3cv
Y3VycmVudC9tc2cwMTcyNi5odG1sDQo+IC0gKEp1bi0yMy0yMDEwIC0gSnVuLTI2LTIwMTApIElQ
UiBEaXNjbG9zdXJlOiBIdWF3ZWkgVGVjaG5vbG9naWVzIENvLiwgTHRkJ3MNCj4gU3RhdGVtZW50
IGFib3V0IElQUiByZWxhdGVkIHRvIGRyYWZ0LWlldGYtZ3Jvdy12YS0wMiBhbmQgMTQgcmVzcG9u
c2VzDQo+IA0KPiBHaXZlbiB0aGlzLCBJIG5lZWQgdG8gZ2FnZSB0aGUgZGVncmVlIHRvIHdoaWNo
IHRoZSBXRyBpcyBzdGlsbCBpbnRlcmVzdGVkIGluIHRoZQ0KPiBkcmFmdC4NCj4gDQo+IENhbiBh
bnlvbmUgc3BlYWsgdG8gdGhlIGxldmVsIG9mIFdHIGludGVyZXN0IGluIHRoaXMgZHJhZnQ/IEFz
IHRoaXMgaXMgYW4NCj4gb3BlcmF0aW9uYWwgV0csIEkgYW0gZXNwZWNpYWxseSBpbnRlcmVzdGVk
IGluIGhlYXJpbmcgZnJvbSBvcGVyYXRvcnMuIEhvd2V2ZXIsDQo+IGFsbCB2aWV3cyBhcmUgd2Vs
Y29tZWQuDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBSb24gQm9uaWNhDQo+
IHZjYXJkOiAgICAgICB3d3cuYm9uaWNhLm9yZy9yb24vcm9uYm9uaWNhLnZjZg0KPiANCj4gDQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEdST1cg
bWFpbGluZyBsaXN0DQo+IEdST1dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9ncm93DQo=

From rbonica@juniper.net  Mon Apr 30 09:56:26 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4CC721F8669; Mon, 30 Apr 2012 09:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level: 
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hb1KAGmAG6Bq; Mon, 30 Apr 2012 09:56:25 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id A1E4B21F8780; Mon, 30 Apr 2012 09:53:35 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT57DjrSffNH4uapLiV0aTHvD+SMaWCbT@postini.com; Mon, 30 Apr 2012 09:53:35 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 30 Apr 2012 09:52:25 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 30 Apr 2012 09:52:25 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 30 Apr 2012 12:52:24 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Mon, 30 Apr 2012 12:52:23 -0400
Thread-Topic: [GROW] draft-ietf-grow-simple-va
Thread-Index: Ac0mlPPR9+6aPszZTa2Ed7ZWJxExAAAXGCxQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net> <4F9E27CC.8070507@raszuk.net>
In-Reply-To: <4F9E27CC.8070507@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 16:56:26 -0000

Robert,

This sounds reasonable to me. Please issue a new version of the draft, as t=
he current version has expired. When you issue a new version, change the fi=
lename, so that it won't look like a WG submission. Also, ping me so that I=
 can send the document on for IETF Last Call.

                                                             Ron

> -----Original Message-----
> From: Robert Raszuk [mailto:robert@raszuk.net]
> Sent: Monday, April 30, 2012 1:49 AM
> To: Ronald Bonica
> Cc: grow@ietf.org; iesg@ietf.org
> Subject: Re: [GROW] draft-ietf-grow-simple-va
>=20
> Ron,
>=20
> >> So, how do we proceed? If you want to demonstrate WG support of
>  >> draft-ietf-grow-simple-va, let the WG LC proceed. If you want to
> >> publish without demonstrating WG support, I would be glad to AD
> >> sponsor that draft.
>=20
> Please proceed with AD sponsorship on this draft.
>=20
> In my view the idea and the draft have already received sufficient
> support within this group, other IETF and IRTF groups as well as
> outside of IETF in various public forums.
>=20
> Thx,
> R.

From jakob.heitz@ericsson.com  Mon Apr 30 12:56:07 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3339021F864D; Mon, 30 Apr 2012 12:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.296
X-Spam-Level: 
X-Spam-Status: No, score=-6.296 tagged_above=-999 required=5 tests=[AWL=0.303,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9DaXWZdCcvN; Mon, 30 Apr 2012 12:56:06 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7666121F864C; Mon, 30 Apr 2012 12:56:06 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3UJg76x014190; Mon, 30 Apr 2012 14:42:09 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 30 Apr 2012 15:42:03 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Ronald Bonica <rbonica@juniper.net>, "robert@raszuk.net" <robert@raszuk.net>
Date: Mon, 30 Apr 2012 15:42:02 -0400
Thread-Topic: [GROW] draft-ietf-grow-simple-va
Thread-Index: Ac0mlPPR9+6aPszZTa2Ed7ZWJxExAAAXGCxQAAVdypA=
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE145B07@EUSAACMS0701.eamcs.ericsson.se>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net> <4F9E27CC.8070507@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 19:56:07 -0000

draft-ietf-grow-simple-va-04 needs another deployment consideration.

Routes in the RIB (not the FIB) are sometimes used
to resolve BGP nexthops and nexthops for static routes.

There is a rule not to resolve such nexthops using the default
route. If routes are removed from the RIB, they will no
longer be able to resolve nexthops. Also, when resolving
nexthops, the resolving routes sometimes carry attributes
that are important to the resolving process. If the
default route is used to resolve nexthops, such attributes
would be lost. Examples of such attributes are
IGP distance (it may be the same as the default) and
whether it is on a tunnel.

The reason for that rule is this:
A non default route says: I can reach the advertised
network and all IP addresses covered by it. If any
IP address covered by this prefix is unreachable,
then it doesn't exist.
A default route says: I can reach many IP addresses,
but obviously not all of them. I can not tell you
which I can actually reach and which I can't.

Routes in the RIB may also be redistributed to other
protocols. If they no longer exist in the RIB, they
will not be redistributed.

These considerations do not break the technique,
but they need to be stated.

--
Jakob Heitz.

-----Original Message-----
From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of Ron=
ald Bonica
Sent: Monday, April 30, 2012 9:52 AM
To: robert@raszuk.net
Cc: grow@ietf.org; iesg@ietf.org
Subject: Re: [GROW] draft-ietf-grow-simple-va

Robert,

This sounds reasonable to me. Please issue a new version of the draft, as t=
he current version has expired. When you issue a new version, change the fi=
lename, so that it won't look like a WG submission. Also, ping me so that I=
 can send the document on for IETF Last Call.

                                                             Ron

> -----Original Message-----
> From: Robert Raszuk [mailto:robert@raszuk.net]
> Sent: Monday, April 30, 2012 1:49 AM
> To: Ronald Bonica
> Cc: grow@ietf.org; iesg@ietf.org
> Subject: Re: [GROW] draft-ietf-grow-simple-va
>=20
> Ron,
>=20
> >> So, how do we proceed? If you want to demonstrate WG support of
>  >> draft-ietf-grow-simple-va, let the WG LC proceed. If you want to
> >> publish without demonstrating WG support, I would be glad to AD
> >> sponsor that draft.
>=20
> Please proceed with AD sponsorship on this draft.
>=20
> In my view the idea and the draft have already received sufficient
> support within this group, other IETF and IRTF groups as well as
> outside of IETF in various public forums.
>=20
> Thx,
> R.
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

From robert@raszuk.net  Mon Apr 30 13:01:21 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD9121F8531 for <grow@ietfa.amsl.com>; Mon, 30 Apr 2012 13:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATaEfdImwc1g for <grow@ietfa.amsl.com>; Mon, 30 Apr 2012 13:01:20 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id D039921F84AF for <grow@ietf.org>; Mon, 30 Apr 2012 13:01:19 -0700 (PDT)
Received: (qmail 6877 invoked by uid 399); 30 Apr 2012 20:01:18 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:robert@raszuk.net@83.31.242.120) by mail1310.opentransfer.com with ESMTPM; 30 Apr 2012 20:01:18 -0000
X-Originating-IP: 83.31.242.120
Message-ID: <4F9EEF87.1050504@raszuk.net>
Date: Mon, 30 Apr 2012 22:01:11 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net> <4F9E27CC.8070507@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net> <7309FCBCAE981B43ABBE69B31C8D213921BE145B07@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE145B07@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 20:01:21 -0000

Hi Jakob,

> draft-ietf-grow-simple-va-04 needs another deployment consideration.
>
> Routes in the RIB (not the FIB) are sometimes used
> to resolve BGP nexthops and nexthops for static routes.

Not sometimes .. Pretty much every time !

> There is a rule not to resolve such nexthops using the default
> route.

That is an option - true.

> If routes are removed from the RIB, they will no
> longer be able to resolve nexthops.

Disconnect ! Simple-va does not remove routes from RIB. It suppresses 
overlapping less specific one.

An option is to suppress all by injecting the default, but this would be 
configurable. Clearly if you allow that you should not disable next hop 
resolution via default. Those two would be mutually exclusive.

> Also, when resolving
> nexthops, the resolving routes sometimes carry attributes
> that are important to the resolving process. If the
> default route is used to resolve nexthops, such attributes
> would be lost. Examples of such attributes are
> IGP distance (it may be the same as the default) and
> whether it is on a tunnel.

Again ... default is the special case as described above. Other then 
that the less specific would have the same next hop as potentially 
suppressed more specific hence IGP distance would be the same.

An implementation may consider not to suppress routes with AIGP 
attribute being significantly different but again I do not find it 
necessary for routing correctness since the main assumption is identical 
next hop.

> The reason for that rule is this:
> A non default route says: I can reach the advertised
> network and all IP addresses covered by it. If any
> IP address covered by this prefix is unreachable,
> then it doesn't exist.
> A default route says: I can reach many IP addresses,
> but obviously not all of them. I can not tell you
> which I can actually reach and which I can't.

Nothing guarantees that you can reach all destinations covered by a 
subnet. (We have been working on negative routes in the past however 
that effort has been shelved).

But I think you are missing the applicability of suppressing to the 
default versus suppressing to the less specific.

1. Suppression to the default(s):

- Applicable to the edge routers in the POP when default route is 
injected from all POP to core boundary routers into the POP.

Note: This mode could be also applicable to AS wide suppression only if 
we could guarantee the exact symmetry of ASBR received BGP updates in 
the AS.

2. Suppression to the less specific:

- Applicable in all cases.

> Routes in the RIB may also be redistributed to other
> protocols. If they no longer exist in the RIB, they
> will not be redistributed.

In the default case - you are correct.

In the suppression by less specific redistribution will work just fine 
routing wise.

The local implementation may tag routes to be suppressed at the BGP to 
RIB boundary and only suppress tagged at the RIB to FIB to address 
redistribution case. However redistribution of BGP to other protocols is 
usually not that good of an idea hence we decided to leave it for now.

> These considerations do not break the technique,
> but they need to be stated.

I am happy to add above clarification to the text in the draft.

Many thx,
R.


>
> --
> Jakob Heitz.
>
> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of Ronald Bonica
> Sent: Monday, April 30, 2012 9:52 AM
> To: robert@raszuk.net
> Cc: grow@ietf.org; iesg@ietf.org
> Subject: Re: [GROW] draft-ietf-grow-simple-va
>
> Robert,
>
> This sounds reasonable to me. Please issue a new version of the draft, as the current version has expired. When you issue a new version, change the filename, so that it won't look like a WG submission. Also, ping me so that I can send the document on for IETF Last Call.
>
>                                                               Ron
>
>> -----Original Message-----
>> From: Robert Raszuk [mailto:robert@raszuk.net]
>> Sent: Monday, April 30, 2012 1:49 AM
>> To: Ronald Bonica
>> Cc: grow@ietf.org; iesg@ietf.org
>> Subject: Re: [GROW] draft-ietf-grow-simple-va
>>
>> Ron,
>>
>>>> So, how do we proceed? If you want to demonstrate WG support of
>>   >>  draft-ietf-grow-simple-va, let the WG LC proceed. If you want to
>>>> publish without demonstrating WG support, I would be glad to AD
>>>> sponsor that draft.
>>
>> Please proceed with AD sponsorship on this draft.
>>
>> In my view the idea and the draft have already received sufficient
>> support within this group, other IETF and IRTF groups as well as
>> outside of IETF in various public forums.
>>
>> Thx,
>> R.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


From jakob.heitz@ericsson.com  Mon Apr 30 16:51:56 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FE221E8114; Mon, 30 Apr 2012 16:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.318
X-Spam-Level: 
X-Spam-Status: No, score=-6.318 tagged_above=-999 required=5 tests=[AWL=0.281,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdCUBMWb7fD3; Mon, 30 Apr 2012 16:51:55 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id B1ED221E8041; Mon, 30 Apr 2012 16:51:55 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3UNprtk014550; Mon, 30 Apr 2012 18:51:55 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 30 Apr 2012 19:51:48 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Mon, 30 Apr 2012 19:51:47 -0400
Thread-Topic: [GROW] draft-ietf-grow-simple-va
Thread-Index: Ac0nDAWJSmNhQVOrSFeJWzHWcNho/wAHnaWw
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE145CC4@EUSAACMS0701.eamcs.ericsson.se>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net> <4F9E27CC.8070507@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net> <7309FCBCAE981B43ABBE69B31C8D213921BE145B07@EUSAACMS0701.eamcs.ericsson.se> <4F9EEF87.1050504@raszuk.net>
In-Reply-To: <4F9EEF87.1050504@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 23:51:56 -0000

On Monday, April 30, 2012 1:01 PM, Robert Raszuk <mailto:robert@raszuk.net>=
 wrote:

> Disconnect ! Simple-va does not remove routes from RIB. It suppresses
> overlapping less specific one.

quote from the draft
...suppress certain routes from being installed in RIB and FIB tables.

If they are "suppressed from being installed in RIB"
then they can't be used to resolve nexthops or to be redistributed.

> However redistribution of BGP to other protocols is=20
> usually not that good of an idea=20

Redistribution of some selected BGP routes does occur.
Not just into IGP and LDP, but also into applications.

--=20
Jakob Heitz.=
