IETF Logo Mail Archive

Re: [Softwires] Comments on draft-ietf-softwire-map-02.txt

Ole Trøan <otroan@employees.org> Fri, 14 September 2012 07:36 UTC

Return-Path: <ichiroumakino@gmail.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 3F0B921F8607 for <softwires@ietfa.amsl.com>; Fri, 14 Sep 2012 00:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.156
X-Spam-Level:
X-Spam-Status: No, score=-2.156 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
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 cicDhgUhDfHB for <softwires@ietfa.amsl.com>; Fri, 14 Sep 2012 00:36:20 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 703DF21F851B for <softwires@ietf.org>; Fri, 14 Sep 2012 00:36:20 -0700 (PDT)
Received: by eekb45 with SMTP id b45so2362944eek.31 for <softwires@ietf.org>; Fri, 14 Sep 2012 00:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=ygEgP6YFj4m27zJyipKW4Bj197eB1KJGJU1lIBMEmLc=; b=rte/7RmV2npgcoqcVVsrpswtE4vIrMn6sjpnyrHcXVwYHcM4TgsXpjx7PTniQuFd6j klxjAYp6UUWv2DJdSiNj2Dpe7Uz3msXednx3NBR/ZHm1cDIo0yPVCUbBYSKu9gp3oQGk 4g9lJjNGtQcHlFW0hPNVXjdJ0Pe7BvAhFCGEeQNg8KIAlWbH26+4XPLQFkBX4AW7FdBp bCRMlVbdpqSZckG2dTO8KPLQ0H0SuChbWaAQBdVWtzfJ82TkvfIWad6auFhYXL62zev9 tws87f9yNwJuWC7W2jbI10xceaeKebLZMepGD8tUwmLU4NWFX5eXEt1bLO1FXwyd794Q zDmg==
Received: by 10.14.221.197 with SMTP id r45mr2201181eep.41.1347608179533; Fri, 14 Sep 2012 00:36:19 -0700 (PDT)
Received: from dhcp-lys01-vla250-10-147-112-145.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id z3sm1838447eel.15.2012.09.14.00.36.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Sep 2012 00:36:18 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_75068600-7B13-4618-9843-A5067BA80077"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Ole Trøan <otroan@employees.org>
In-Reply-To: <CAC8QAcc21HL_YUB98=n+M_BVmhJb3hqDKhsAPTOD52L1LiCmqA@mail.gmail.com>
Date: Fri, 14 Sep 2012 09:36:19 +0200
Message-Id: <01874DCB-11A0-42E2-91BD-FF16B03985AF@employees.org>
References: <CAC8QAcc21HL_YUB98=n+M_BVmhJb3hqDKhsAPTOD52L1LiCmqA@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.1278)
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Comments on draft-ietf-softwire-map-02.txt
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, 14 Sep 2012 07:36:21 -0000

Bechet,

> I have some comments on this draft.
> 
> Regarding Section 5, I am curious why we need the mapping, i.e.
> Section 5 if we are doing MAP-E? i.e. NAT44'ed IPv4 packet is
> encapsulated in IPv6 using RFC 2473. RFC2473 defines quite in detail
> in Section 5 on Tunnel IPv6 Header almost everything needed.

MAP-E does everything MAP does. support of mesh mode, stateless BRs...
without mapping how would that be achieved?

> More specific comments: what is the relationship of this draft with
> the original MAP-E draft, draft-mdt-softwire-map-encapsulation-00?
> That draft described in detail how RFC 2473 would be used which is
> missing in draft-ietf-softwire-map-02. OTOH draft-ietf-softwire-map-02
> does not even reference draft-mdt-softwire-map-encapsulation-00, why?

draft-ietf-softwire-map has evolved from draft-mdt-softwire-map-encapsulation and is meant
to incorporate all the significant parts of it. something may have fallen out in editing,
if so please propose text.

cheers,
Ole

v2.23.0 | Report a Bug | By Email