Re: [Softwires] draft-ietf-softwire-lw4over6 excluding Well Known Ports

Wojciech Dec <wdec.ietf@gmail.com> Mon, 02 June 2014 19:27 UTC

Return-Path: <wdec.ietf@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 9A5FD1A0275 for <softwires@ietfa.amsl.com>; Mon, 2 Jun 2014 12:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 DbkU1AQX95k2 for <softwires@ietfa.amsl.com>; Mon, 2 Jun 2014 12:27:31 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1C81A0223 for <softwires@ietf.org>; Mon, 2 Jun 2014 12:27:30 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id l18so5678266wgh.35 for <softwires@ietf.org>; Mon, 02 Jun 2014 12:27:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TUrY0veiKPXMufQQhT+hvOQnAitYUI1We+S3mKxVEFM=; b=M5X1bhRdqIRobMG0L3DTRqUwJAUrkyoAHoLJGZdlQXAYV39PcgPQJH2GlOTZI5LTwa ToXQKEZfEQDgDUeFsWOipw3oIV61OzEyAXrUlYV10kJ2KIIPIF9/E7X7ychyD3VniJHF 7iW86dDYxHo30kY03Xcau5lEtD7EculZ7hkRCAKIGDak6GLz78gVGfnEcraBbnGPzVRh 8huvPNmY+GPU0zXwbJo7mz1Cg5SE/mccCpAJGtaj0e5ek88F+XcY6bhZ8Nv1jdcNfiFr cHQxF21f4o/Cq40QbdEe2Lj1NHrli8RNlnKzjlqBEEIx7sq0GZF5aK16GkxwIAAkthni L4Cg==
MIME-Version: 1.0
X-Received: by 10.180.210.237 with SMTP id mx13mr25203177wic.49.1401737243879; Mon, 02 Jun 2014 12:27:23 -0700 (PDT)
Received: by 10.194.165.71 with HTTP; Mon, 2 Jun 2014 12:27:23 -0700 (PDT)
In-Reply-To: <538CB982.2060502@gmail.com>
References: <53422B8F.2020109@ericsson.com> <37A243DD-5249-4070-AB19-6DFFCFE17AA7@gmx.com> <DC98AF70-DBF1-48AD-8699-2FC4E645FF40@cisco.com> <C3B32B71-79EE-408F-A92C-D40021DC9A5A@gmx.com> <92E51E75-2914-421F-B222-7478EC3D6A02@cisco.com> <BBFBDEAA-0D2B-4A74-86E4-88824712EA26@gmx.com> <CAFFjW4igsiqS5yNUECerMzpZSkmPaL28sqef1usZdxt87y1jEw@mail.gmail.com> <538CB982.2060502@gmail.com>
Date: Mon, 02 Jun 2014 21:27:23 +0200
Message-ID: <CAFFjW4jxY=fjCszomzHyWhYtb+1QE+bN-afp_Qi5_32WxUydJg@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c258607d6fc704fadf6295"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/lBILhfFeYmrLQsPqvyy3JIQ4G5I
Cc: draft-ietf-softwire-lw4over6@tools.ietf.org, Ole Troan <ot@cisco.com>, Yong Cui <cuiyong@tsinghua.edu.cn>, Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] draft-ietf-softwire-lw4over6 excluding Well Known Ports
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: Mon, 02 Jun 2014 19:27:33 -0000

Well, I'm referring to the "RECOMMENDED" part. If the recommendation is NOT
to allocate ports 0-1024, then this effectively recommends that a-bits=6.
Moreover the meaning of SHOULD vs RECOMMEND should be questioned. The
latter is not a regular normative term, and arguably if the recommendation
is for excluding 0-1024 then a=6 looks like the SHOULD. If anyone wants the
full port set, then a=0 would be an obvious consequence.


On 2 June 2014 19:50, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> Not sure how you read that, but it can be fixed by putting a comma after
> "SHOULD be 0" and replacing "to allocate" with "thus allocating".
>
> Tom
>
>
> On 02/06/2014 12:14 PM, Wojciech Dec wrote:
>
>> Uhm, this appears to mean that the RECOMMENDED a-bits SHOULD be 6.
>>
>>
>> On 26 May 2014 13:24, Ian Farrer <ianfarrer@gmx.com> wrote:
>>
>>  Hi,
>>>
>>> This one slipped my mind….
>>>
>>>  From a discussion with Ole during the MAP dhcp last call, there was a
>>> discussion about the exclusion of provisioning WKPs to CPEs -
>>> http://www.ietf.org/mail-archive/web/softwires/current/msg06010.html
>>>
>>> In previous versions, the lw4o6 used to reference
>>> sun-dhc-port-set-option,
>>> which also stated that the WKPs should not be assigned. This advice got
>>> lost when changing to reference map-dhcp for PSID format.
>>>
>>> Here’s a wording change proposal to resolve this:
>>>
>>> Section 5.1
>>>
>>> Original text (last sentence, para 7):
>>>
>>> "For lw4o6, the  number of a-bits SHOULD be 0."
>>>
>>> Proposed change:
>>>
>>> "For lw4o6, the number of a-bits SHOULD be 0 to allocate a single
>>> contiguous port set to each lwB4.
>>>
>>> Unless a lwB4 is being allocated a full IPv4 address, it is RECOMMENDED
>>> that PSIDs containing the well-known ports (0-1023) are not allocated to
>>> lwB4s.”
>>>
>>> Please let me know if you are OK with the proposed change.
>>>
>>> cheers,
>>> Ian
>>>
>>>
>>>>  Good spot on the WKP exclusion. Before the lw4o6 draft was updated to
>>>>>
>>>> reference map-dhcp for configuration,  the port configuration was
>>> described
>>> in sun-dhc-port-set-option, which also stated that the WKPs should not be
>>> assigned. This advice got lost when changing to reference map-dhcp. I’ll
>>> make a suggested text update for the lw4o6 draft to fix this. Does that
>>> work for you?
>>>
>>>>
>>>> yes, that would be good.
>>>>
>>>> cheers,
>>>> Ole
>>>>
>>>>
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>>
>>>
>>
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
>>