IETF Logo Mail Archive

Re: [IPsec] clariciations for draft-sathyanarayan-ipsecme-advpn-03

"Frederic Detienne (fdetienn)" <fdetienn@cisco.com> Fri, 17 January 2014 09:57 UTC

Return-Path: <fdetienn@cisco.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765D41ADFC0 for <ipsec@ietfa.amsl.com>; Fri, 17 Jan 2014 01:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level:
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XH5jubSNHQ2A for <ipsec@ietfa.amsl.com>; Fri, 17 Jan 2014 01:57:53 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDD71ADFB6 for <ipsec@ietf.org>; Fri, 17 Jan 2014 01:57:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2350; q=dns/txt; s=iport; t=1389952661; x=1391162261; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=8a/rjcKXJ5Cj6kUA0smmcWEuk5qtcAJKSqDxEB2u2F0=; b=TfjHskKeQjLDjoj/u/XI+nQYsL/wvPZ8F30bORHTUWwtY4vR3BagMuZb PTmjyuwr3r/iQwK+irQk0J7rn2JSO60IkXQOmI6jE4a6RE3KsvzBkq/Gt ruT6NLQrQCR1WDafTNcsVfjcIxHTYr+e5JI1R7qdlr9PWMeECV9kLILqn 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAJFf2FKtJXG8/2dsb2JhbABZgws4VqkikW+BDxZ0giUBAQEDAQEBATc0BgoLAgEINhAnCyUCBBOHfAgNxTQTBI4oJDqDJIEUBJghkheDLYFpQQ
X-IronPort-AV: E=Sophos;i="4.95,670,1384300800"; d="scan'208";a="298053226"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 17 Jan 2014 09:57:40 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0H9ve6E004084 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ipsec@ietf.org>; Fri, 17 Jan 2014 09:57:40 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.243]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Fri, 17 Jan 2014 03:57:40 -0600
From: "Frederic Detienne (fdetienn)" <fdetienn@cisco.com>
To: "<ipsec@ietf.org> WG" <ipsec@ietf.org>
Thread-Topic: [IPsec] clariciations for draft-sathyanarayan-ipsecme-advpn-03
Thread-Index: AQHPEHmWVSfQ3H7ZOEi1TNp+NhtSp5qJGL6A
Date: Fri, 17 Jan 2014 09:56:51 +0000
Message-ID: <CDABA9E0-1655-4F48-AF9B-99C15EFB8EF9@cisco.com>
References: <7DC80D6C-3342-43C3-9407-E5D25CB5F5CD@cisco.com>
In-Reply-To: <7DC80D6C-3342-43C3-9407-E5D25CB5F5CD@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.60.74.189]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10BDB0C84F350A439A1C5EA6198244F2@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [IPsec] clariciations for draft-sathyanarayan-ipsecme-advpn-03
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 09:57:54 -0000

Hi,

I would like to re-iterate the importance of clarifying the points below as it is not possible to assess the performances, relevance and interoperability of draft-sathyanarayan-ipsecme-advpn-03 at this stage - - these are all important issues to potential users of this techology.

Thank you,

 Frederic Detienne


On 13 Jan 2014, at 17:07, Frederic Detienne (fdetienn) <fdetienn@cisco.com> wrote:

> Hi,
> 
> In reviewing the discussions over the past few weeks, there appear to be a number of issues concerning draft-sathyanarayan-ipsecme-advpn-03 that require further clarification.
> 
> It would be useful for the working group if the following aspects of draft-sathyanarayan-ipsecme-advpn-03 were clarified:
> 
> 1. scaling & general networking:
>  1.1 It does appear this proposal has a limit of 256 networks. Is this correct ? How do nodes negotiate SA's when there are more than 256 prefixes on each side ? For reference, RFC5996 does not offer the ability to negotiate more than 256 prefixes in the TSi TSr payloads.
> 
>  1.2 What happens when a prefix administratively changes from behind one branch to another ? How do servers get notified about that ?
> 
>  1.3 How is VLSM taken into consideration (Variable Length Subnet Masking). E.g. long prefix behind one branch and a short prefix behind another
> 
>  1.4 How does a hub decide which Security Association to use when to spoke devices decide to advertise the same prefix ?
> 
> 2. multicast:
> 
> 2.1 There does not appear to be a specification of Multicast in this proposal. This is a key requirement for some of the ADVPN sponsors. How does multicast  work ?
> 
> 2.2 How are SA's negotiated and how do applications request multicast traffic to be sent ?
> 
> 3.interoperability. draft-sathyanarayan-ipsecme-advpn-03 does not mention how a server/hub learns about networks behind other servers
> 
> 3.1 what are the steps a server should take to establish a network with other servers
> 
> 3.2 how is topology and reachability information exchanged between servers
> 
> 
> Thank you,
> 
> 	Frederic Detienne
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email