[Softwires] review of draft-ietf-softwire-map-radius-14

hezihao <hezihao9512@gmail.com> Mon, 12 March 2018 05:40 UTC

Return-Path: <hezihao9512@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 140E9126DFF for <softwires@ietfa.amsl.com>; Sun, 11 Mar 2018 22:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level:
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ZTi94qmucctJ for <softwires@ietfa.amsl.com>; Sun, 11 Mar 2018 22:40:47 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 A967D1204DA for <softwires@ietf.org>; Sun, 11 Mar 2018 22:40:47 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id k79-v6so9829226ita.2 for <softwires@ietf.org>; Sun, 11 Mar 2018 22:40:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:subject:mime-version :content-transfer-encoding; bh=AqLnAFLd9q8ME9GIMfzBfEToPxoOV/dmh+ryJoqb0qA=; b=OxqbRk/u5nfk695nbNqfYSJX9nYrYceAE2QApVdhYr2ptmtS8NWLfLzQGETQGj0zri GKMrCZ2degh9HkUn2qy/ckwOXZaT/DX19dAuVa6Q1hkGlZfWv2lER4NimCLfWat/xdRM v+2WaBoImZBLRcqcGNB5TYmm9FsPs7wE5wJyKJrRtQfTdkR6OUdKeG343s0vQ9PKUHCR Wu6DGfuJ1xk3QAfp7iezaZXMldJsJAlZUeWZXbji2DKBIQDPPwZOAQmEPT/I/zstNsiD 4u7cryqLigzDRQYNSU8ZKiB5XHtVXADXNQCaLBpVfVCcoQX8F/8dYqHWxFcxZt3QI33I sGBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:subject:mime-version :content-transfer-encoding; bh=AqLnAFLd9q8ME9GIMfzBfEToPxoOV/dmh+ryJoqb0qA=; b=c2aUxf2XHMkm1gVl9DBQ0WrMofVVReCyIKlDWnuXEVk16YonKuhIzuEQDzC7o+26+d q+keFdTKFVCv5ZZpMejwxcDp95Yt23UaWqLkobF4wEluuzeIn97spotbkk/TprBbjXNG vhYLWDg6WksMG1l9eIWHGj4hN+6wGZ/SwgPAo3CXKZMIg48SuX379Hd/ZyhuZBJXb+tB zD3yArZbtJcB8dGHlSXmfHJ3LK7UbWUXTh4F/Y6lvYvAXziJP9suobF80Lgyno8xrM8L UVhc8n+8YxGnX9NGXmn6Q0dm+qC3d4jU2SqiJ/mZNHBy8AuHWgcBLHn1OYjcp41/IBOA gN6Q==
X-Gm-Message-State: AElRT7EaWMQYLWVfQDVN307+v2vsmW4HUa71PIxYNHHeH4bOrcQgzaRf bIC7nk3gTztHjWvpKH5612Srrh2x
X-Google-Smtp-Source: AG47ELtFK1bS0xrBaJLQdaC9aXn/PIepthngIWAtOqrkWine2AnzEDqrlH+ZwEZ9eVVi5GmIHmOJcw==
X-Received: by 10.36.94.197 with SMTP id h188mr7091129itb.141.1520833246883; Sun, 11 Mar 2018 22:40:46 -0700 (PDT)
Received: from DESKTOP-7HBCU2Q ([103.65.41.148]) by smtp.gmail.com with ESMTPSA id h63sm2710654ith.32.2018.03.11.22.40.45 for <softwires@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Mar 2018 22:40:46 -0700 (PDT)
Date: Mon, 12 Mar 2018 13:42:49 +0800
From: hezihao <hezihao9512@gmail.com>
To: "softwires@ietf.org" <softwires@ietf.org>
Message-ID: <46A82FF3-0DDC-4373-8EF9-9A0C2853A4BE@gmail.com>
X-Mailer: MailMasterPC/4.3.1.1011 (Windows 10 RS3)
X-CUSTOM-MAIL-MASTER-SENT-ID: F72ACFD8-B944-4242-AEE7-C9E566A52327
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/gC6LnJoa9nv5KGHdUS7eV0GANWw>
Subject: [Softwires] review of draft-ietf-softwire-map-radius-14
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Mar 2018 05:40:49 -0000

Hi authors,

Here is a review of version-14.

Generally, this draft looks good to me, only with some language issues. I list them out in the following. Glad if these comments could help improve this draft.

 

BR,

Zihao

 

 



1)   Section 3, step 2

This sentence is a little cumbersome. This incurs ambiguity.

For example, it’s a little hard for me to understand what is “to the RADIUS server”, what “requests authentication”, what “will be defined in the next section”.

I would think that splitting the monolithic sentence into some shorter ones would be better, which might be something like this.

“When the BNG receives the Solicit message, it should initiate a radius Access-Request message. In this message, a User-Name attribute (1) should be filled with a CE MAC address, interface-id, or both. In addition, in this message, a User-password attribute (2) should be filled with the shared password that has been preconfigured on the DHCPv6 server. *** requests authentication. *** will be defined in the next section.”

 

2)   Section 1, Para 2

“The BNG is assumed to embed a DHCPv6 server function that allows...”

 

Probably this is a grammar thing. I can’t figure out who is assumed to be embedded in whom from this expression without some inferences. I suppose that you want to speak this sentence in active voice as “We are assumed to embed a function in the BNG”, so the passive voice version might be

“A DHCPv6 server function is assumed to be embedded in the BNG”

or “In the BNG a DHCPv6 server function is assumed to be embedded.”

 

3)   Section 1, Para 3

“The RADIUS attributes designed in this document are especially for the MAP-E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing enough information…”

 

It’s a little bit difficult for me to understand what “provides enough information”, the attributes or three RFCs? Possibly it’s better to state this clearly.

 

4)   Section 3, step 6

“After receiving the client's Request message, containing the corresponding S46 Container option, the BNG SHOULD reply to…”

 

Since by “containing the option” you mean that “the message contains the option”, I would suppose that it would be better to delete the comma here. Otherwise, “containing the corresponding option” might be thought as some sort of conditions/assumptions (adverbial) of the next sentence.

 

5)    Section 4.6.2

“there are k bits in the port number representing valid of PSID.”

I think you probably omitted a word after the word 'valid', since 'valid' is an adjective.

Or is it intended as “validity”?

 

6)   Section 4.10,

“0+”

can't find '0+' in the table.