Re: [RPSEC] BGP question - private
"tom.petch" <cfinss@dial.pipex.com> Fri, 23 March 2007 18:11 UTC
Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HUoEr-0006lF-9I; Fri, 23 Mar 2007 14:11:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HUoEq-0006fA-3V
for rpsec@ietf.org; Fri, 23 Mar 2007 14:11:44 -0400
Received: from astro.systems.pipex.net ([62.241.163.6])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUoEo-0000E3-Pj
for rpsec@ietf.org; Fri, 23 Mar 2007 14:11:44 -0400
Received: from pc6 (1Cust249.tnt8.lnd4.gbr.da.uu.net [62.188.137.249])
by astro.systems.pipex.net (Postfix) with SMTP id 2D8ABE000137;
Fri, 23 Mar 2007 18:11:26 +0000 (GMT)
Message-ID: <000701c76d6d$f33be4c0$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Susan Hares" <skh@nexthop.com>,
<rpsec@ietf.org>
References: <6F44D7F6B24A8F4DA0AB46C9BE924F0209F07D5A@VS4.EXCHPROD.USA.NET>
Subject: Re: [RPSEC] BGP question - private
Date: Fri, 23 Mar 2007 09:51:47 +0100
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-Spam-Score: 0.2 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc:
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
<mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
<mailto:rpsec-request@ietf.org?subject=subscribe>
Errors-To: rpsec-bounces@ietf.org
----- Original Message ----- From: "Susan Hares" <skh@nexthop.com> To: <rpsec@ietf.org> Sent: Wednesday, March 21, 2007 10:43 AM Subject: [RPSEC] BGP question - private Rpsec group: Is rpsec specification protecting the just current BGP or does rpsec intend to protect future TLVs Inside BGP? Sue A well designed protocol gives you the option, for example with option bits that allow such as - include even if you do not understand - discard if you do not understand - stop dead and abandon if you do not understand some of which BGP4 and OSPFv3 have. Meta-protocol engineering:-) Tom Petch Sue Hares (private ietf citizen) -------------------------------------------------------------------------------- > _______________________________________________ > RPSEC mailing list > RPSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/rpsec > _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec
- [RPSEC] BGP question - private Susan Hares
- Re: [RPSEC] BGP question - private tom.petch