Re: [Softwires] I-D Action: draft-ietf-softwire-map-12.txt
"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Sun, 15 February 2015 08:20 UTC
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1F871A1A64 for <softwires@ietfa.amsl.com>; Sun, 15 Feb 2015 00:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 poGr15hEY_HU for <softwires@ietfa.amsl.com>; Sun, 15 Feb 2015 00:20:09 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15C3F1A1A60 for <softwires@ietf.org>; Sun, 15 Feb 2015 00:20:09 -0800 (PST)
Received: by iecvy18 with SMTP id vy18so28125201iec.13 for <softwires@ietf.org>; Sun, 15 Feb 2015 00:20:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=KlDIoj/IHCd3Jy2m8NxJp/M752RmPK0EIH4ATCYAclo=; b=NndgG/LAnncB5c4+ZvMsSZnPLADIK3Iid/edVi+5uY9IVUS3jFtbKZ16JgVUxS/oN+ zJr0jCWIg1lhiiR5mWfXd1fwPDRECr1lcSEzkiR5UbVSBrFnRmD71bzhe7eVGBj9x+GJ GqnxGZDTkWalHFGGDwtLmaksaliCkO8LvzZLuWCFi7qL1B4pm+tsmN71F585M9bHBWHg IDIvoZJBRjCZJl3pj70s4gxAlFdG+/pcLRIimkP/kNT8/R7kT06KhYfi/+LK/oIAk2DV CXin3eNUfq9zk+mbXMSb97gmVeesWab0k5M6YRdlqA8E9j1xpEDoK4FZhIF9p4KFNkLd UpNw==
X-Received: by 10.43.76.9 with SMTP id zc9mr23537476icb.84.1423988408500; Sun, 15 Feb 2015 00:20:08 -0800 (PST)
Received: from PC ([218.241.109.163]) by mx.google.com with ESMTPSA id k13sm4257799iod.38.2015.02.15.00.20.05 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 15 Feb 2015 00:20:08 -0800 (PST)
Message-ID: <54e056b8.0d886b0a.535d.ffffcb06@mx.google.com>
X-Google-Original-Message-ID: <018701d048f8$51289dd0$f379d970$@yeh.sdo@gmail.com>
From: Leaf Yeh <leaf.yeh.sdo@gmail.com>
To: 'Ole Troan' <ot@cisco.com>
References: <20141124073912.16300.97956.idtracker@ietfa.amsl.com>
In-Reply-To: <20141124073912.16300.97956.idtracker@ietfa.amsl.com>
Date: Sun, 15 Feb 2015 16:20:50 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0188_01D0493B.5F4BDDD0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdAHudUkv7u6AEbGSiayAcdILTjuzBBGQ4dw
Content-Language: zh-cn
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/pvDSO7FuqHOer1tNpVN2Bfd0N_c>
Cc: softwires@ietf.org
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-12.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 15 Feb 2015 08:20:13 -0000
I got a late read on this draft, and may find some editorial nits: #1. In sec. 3, " End-user IPv6 prefix: The IPv6 prefix assigned to an End-user CE by other means than MAP itself. E.g., Provisioned using DHCPv6 PD [RFC3633], assigned via SLAAC [RFC4862], or configured manually. It is unique for each CE. " Q. Does the above means ' End-user IPv6 prefix ' includes 's bits' (the subnet ID) in Fig.3? But in sec. 5.2, " The MAP IPv6 address is created by concatenating the End-user IPv6 prefix with the MAP subnet identifier (if the End-user IPv6 prefix is shorter than 64 bits) and the interface identifier as specified in Section 6. " Q. Does the above means ' End-user IPv6 prefix ' does not include 's bits' (the subnet ID) in Fig.3? I guess we could include 's bits' (the subnet ID= MAP subnet identifier) into ' End-user IPv6 prefix '. And in sec. 6, " If the End-user IPv6 prefix length is larger than 64, the most significant parts of the interface identifier is overwritten by the prefix. " Q. Does the above means ' End-user IPv6 prefix ' includes 's bits' (the subnet ID) in Fig.3? #2. In sec. 5.1, " For 'a' > 0, A MUST be larger than 0. This ensures that the algorithm excludes the system ports. For the default value of a (6), the system ports, are excluded by requiring that A be greater than 0. Smaller values of a excludes a larger initial range. E.g., a = 4, will exclude ports 0 - 4095. The interval between initiaL port numbers of successive contiguous ranges assigned to the same user is 2^(16-a). " I prefer the above sentence could be " For 'a' > 0, 'A' MUST be larger than 0. This ensures that the algorithm excludes the system ports. Smaller values of 'a' excludes a larger initial range; e.g. 'a' = 4, will exclude ports 0 - 4095. The interval between initial port numbers of successive contiguous ranges assigned to the same user is 2^(16-a). " #3. In Fig.7 of sec. 5.3, “ +----------+ +------------+ |IPv4 sufx| |Port-Set ID | +----------+ +------------+ ” I prefer the above ‘sufx’ could to be ‘suffix’. #4. In sec.6, “ The PSID field is left-padded to create a 16 bit field. For an IPv4 prefix or a complete IPv4 address, the PSID field is zero.” Q. Does the about ‘zero’ means the value of the PSID=0x 00, or the length of the PSID is zero? I guess it means the former, right? #5. In Fig.8 of sec.6, “The Interface identifier format of a MAP node is described below. | 128-n-o-s bits | | 16 bits| 32 bits | 16 bits| +--------+----------------+--------+ | 0 | IPv4 address | PSID | +--------+----+-----------+--------+ ” I think BR does not need to use the above IID. I prefer to replace the word ‘MAP node’ to be ‘MAP CE’. Right? The above format looks like ‘128-n-o-s =64, but that is not always true. I prefer the IID format of MAP CE could be: | 128-n-o-s bits | | <=16 bits| 32 bits | 16 bits| +--------+----------------+--------+ | all 0s | IPv4 address | PSID | +--------+----+-----------+--------+ ” #6. In sec. 8.1, “ Secondly, the node extracts the source IPv4 address and port from the IPv4 packet embedded inside the IPv6 packet. If they are found to be outside the acceptable range, the packet MUST be silently discard and a counter incremented to indicate that a potential spoofing attack may be underway.” I guess the better to substitute the above word ‘embedded’ could be ‘encapsulated’, right? #7. In sec. 11 “ They cannot exist with MAP because each BRs checks that the IPv6 source address of a received IPv6 packet is a CE address based on Forwarding Mapping Rule. ” I think BRs check that the IPv6 source address of a received IPv6 packet is a CE address based on Basic Mapping Rule, and check that the IPv6 destination address of a received IPv6 packet is a CE address based on Forwarding Mapping Rule, right? Best Regards, Leaf -----Original Message----- From: Softwires [mailto:softwires-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Monday, November 24, 2014 3:39 PM To: i-d-announce@ietf.org Cc: softwires@ietf.org Subject: [Softwires] I-D Action: draft-ietf-softwire-map-12.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Softwires Working Group of the IETF. Title : Mapping of Address and Port with Encapsulation (MAP) Authors : Ole Troan Wojciech Dec Xing Li Congxiao Bao Satoru Matsushima Tetsuya Murakami Tom Taylor Filename : draft-ietf-softwire-map-12.txt Pages : 32 Date : 2014-11-23 Abstract: This document describes a mechanism for transporting IPv4 packets across an IPv6 network using IP encapsulation, and a generic mechanism for mapping between IPv6 addresses and IPv4 addresses and transport layer ports. The IETF datatracker status page for this draft is: <https://datatracker.ietf.org/doc/draft-ietf-softwire-map/> https://datatracker.ietf.org/doc/draft-ietf-softwire-map/ There's also a htmlized version available at: <http://tools.ietf.org/html/draft-ietf-softwire-map-12> http://tools.ietf.org/html/draft-ietf-softwire-map-12 A diff from the previous version is available at: <http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-12> http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: <ftp://ftp.ietf.org/internet-drafts/> ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Softwires mailing list <mailto:Softwires@ietf.org> Softwires@ietf.org <https://www.ietf.org/mailman/listinfo/softwires> https://www.ietf.org/mailman/listinfo/softwires
- [Softwires] I-D Action: draft-ietf-softwire-map-1… internet-drafts
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Xing Li
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Leaf Yeh
- Re: [Softwires] I-D Action: draft-ietf-softwire-m… Ole Troan