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

"Frederic Detienne (fdetienn)" <fdetienn@cisco.com> Mon, 13 January 2014 16:07 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 6A2581AE184 for <ipsec@ietfa.amsl.com>; Mon, 13 Jan 2014 08:07:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level:
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 wFfxuxyXCe2R for <ipsec@ietfa.amsl.com>; Mon, 13 Jan 2014 08:07:54 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id C9AD71AE04F for <ipsec@ietf.org>; Mon, 13 Jan 2014 08:07:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1702; q=dns/txt; s=iport; t=1389629264; x=1390838864; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=IynpQlF9fU5liJju0BK/T4Mex7KoplZG/WQYsxn0mrQ=; b=Az7VY6YZZHBaqqCXrLKk3nyTIiScF+CA+74nS3QdIVQ5KSeWhI/2TkAp fFau/PZ8kksSdAVAO/K5UNYZxLq2MK+ZaD++s6sALI/0xgAXL4qxwJEhQ LZTC+P7aMTqweLe58zbg5p46qHkGZv8okRSN9nOFzYO+H7rWv93lyCnLN Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FACoO1FKtJXHB/2dsb2JhbABagwuBDqhLkjcWdIIsOlEBPkInBIgXmnOpYxeOMIQCgRMEmBeSFYMtgWlB
X-IronPort-AV: E=Sophos;i="4.95,653,1384300800"; d="scan'208";a="12489488"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-8.cisco.com with ESMTP; 13 Jan 2014 16:07:43 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0DG7hrW008655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ipsec@ietf.org>; Mon, 13 Jan 2014 16:07:43 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.243]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 10:07:43 -0600
From: "Frederic Detienne (fdetienn)" <fdetienn@cisco.com>
To: "<ipsec@ietf.org> WG" <ipsec@ietf.org>
Thread-Topic: clariciations for draft-sathyanarayan-ipsecme-advpn-03
Thread-Index: AQHPEHmWVSfQ3H7ZOEi1TNp+NhtSpw==
Date: Mon, 13 Jan 2014 16:07:10 +0000
Message-ID: <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: <876BABD1101A6340A075DF52245FCC1A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [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: Mon, 13 Jan 2014 16:07:56 -0000

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