[Softwires] MAP-E 1:1 for HA

"Lee, Yiu" <Yiu_Lee@Cable.Comcast.com> Fri, 09 November 2012 19:43 UTC

Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6460E21F8564 for <softwires@ietfa.amsl.com>; Fri, 9 Nov 2012 11:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.144
X-Spam-Level:
X-Spam-Status: No, score=-104.144 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1GHuZlFkl9v for <softwires@ietfa.amsl.com>; Fri, 9 Nov 2012 11:43:14 -0800 (PST)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF1321F8552 for <softwires@ietf.org>; Fri, 9 Nov 2012 11:43:14 -0800 (PST)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.41254637; Fri, 09 Nov 2012 12:17:51 -0700
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.131]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Fri, 9 Nov 2012 14:43:08 -0500
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: MAP-E 1:1 for HA
Thread-Index: AQHNvrJUhwE7DtDnmkmwZYkUbhoBVw==
Date: Fri, 09 Nov 2012 19:43:08 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD453B499F@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3435316988_1115972"
MIME-Version: 1.0
Subject: [Softwires] MAP-E 1:1 for HA
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 19:43:15 -0000

I have a question for the HA design concept of MAP-E 1:1. The central theme
of MAP-E is to make BR as stateless as possible and use Anycast address to
identify the MAP-E BR. However, if we use MAP-E 1:1 mode, the operator must
have to pre-provision all the subscribe rules to all the BRs sharing the
same Anycast address for reliable HA. This requires operators to carefully
plan out which BRs support which subscribers. It is because BR is
"per-subscriber stateful" in MAP-E 1:1 mode. Compared to the MAP-E design,
HA in MAP-E only requires the operators to use the same set of rules to
cover the entire domain. IMHO, this contradicts  the original spirit of
stateless solution and always puzzles me why MAP-E 1:1 bears the MAP-E name.
MAP-E and 1:1 MAP-E are two completely different solutions and target to
different deployment scenarios. I would love to hear others to comment in
the ML how to resolve this issue.

Thanks,
Yiu