Re: [Softwires] Fwd: New Version Notification for draft-ietf-softwire-map-radius-07.txt

tianxiang li <peter416733@gmail.com> Tue, 12 July 2016 03:41 UTC

Return-Path: <peter416733@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 321E812D73A for <softwires@ietfa.amsl.com>; Mon, 11 Jul 2016 20:41:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 bu1G_QUSTtHV for <softwires@ietfa.amsl.com>; Mon, 11 Jul 2016 20:41:39 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 10D8912D595 for <softwires@ietf.org>; Mon, 11 Jul 2016 20:41:39 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id w18so5229082oiw.3 for <softwires@ietf.org>; Mon, 11 Jul 2016 20:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Czls0zA0sWP0Z7cOP9TPxZApuWDcUb6t2hiDU5RBGVw=; b=hwJGQTOk4HKzXNAwrT+wIFjHLeEwfEGUv/pu5WVb9hxKpBa3kLKAxJNQgWMs28fsoH jWEUHS6rD1eF1Oowiw1ZA32Gs4vRybpQFfqTQbNAshBJ8VZ/WN9ZzXsEqbtgk65PyArX sQ8cIFZ0RCvdY2prijJt+l99jfzK0aCvtW8/cmNh6r0nTuPDL7+2UsNy2o+N7RidkNV0 RCWxbqwF/tyN7ZimgFiQwzreC5V9+QjYhAAoU5LnEv0wchr6blmH6EMnlfdwPkXIAQUl sBy0x4ZMjGaCoTWLYNsMXzpIzIT3rNWkq/U9HmGL3r02tu5iLVxo+nBBeqo7j6og0LOl nfdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Czls0zA0sWP0Z7cOP9TPxZApuWDcUb6t2hiDU5RBGVw=; b=KHZc+Ll4hcFhEfOPXZf+LVwEWH79Up4T8d6FgE7S8OBHDf2mwW6UWRORu/No7BhJos 1oFWX2nGPUiRuBVAl3FnqxukuK55cJeCr/vvKl0VBFHTj0sSUbUo66EaZsU3Ms8L1RLA tfr/R4impiG0TVN1pUPgKDE8xbnxT0A1EHqAnbAvvxQihy/HxJVRY2xsLyeilUcaoUNH 0Z6rCTixpUU70x0QOfzSPBzTZx1QDmgusisNbVtLkqlgMtFYKlpjQvD/yBnEqpT70+S9 wBDwVlPo1RBII4jVr0wmZJ4TTQ7C+TS8XofxLMbYW6lsuohVLiNRLo4ODC1eCwhFpKkq iw9g==
X-Gm-Message-State: ALyK8tJc+sHjYyNvudThso/wVClfWAul6OHhza+iGKLhRFgWz0cYQAdURaKBEHJ6VYPLyGdaHZNUDf01hwysWw==
X-Received: by 10.202.184.65 with SMTP id i62mr12350275oif.94.1468294898388; Mon, 11 Jul 2016 20:41:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.202 with HTTP; Mon, 11 Jul 2016 20:40:59 -0700 (PDT)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008DCEAB2@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20160707112101.23670.83042.idtracker@ietfa.amsl.com> <CAFx+hEP1re+Rj_jRjYasZY14eEgwqHXvHwD1b1eH6Ud_5WRaUw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933008DCEAB2@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: tianxiang li <peter416733@gmail.com>
Date: Tue, 12 Jul 2016 11:40:59 +0800
Message-ID: <CAFx+hENiRQE+5Ha0_vSst4=ccWt3mP5QtCeb9_dCrcVNX5Syiw@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary=001a113cd19ad814ea0537680b59
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/tfWqo8mu0h5MRHhy3vkg94vriuM>
Cc: softwires@ietf.org
Subject: Re: [Softwires] Fwd: New Version Notification for draft-ietf-softwire-map-radius-07.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Jul 2016 03:41:44 -0000

Hi Med,

Thank you for your comments.
Please see inline(TX>)

Cheers,
Tianxiang

2016-07-11 15:55 GMT+08:00 <mohamed.boucadair@orange.com>om>:

> Hi Tianxiang,
>
>
>
> Please see inline.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Softwires [mailto:softwires-bounces@ietf.org] *De la part de*
> tianxiang li
> *Envoyé :* jeudi 7 juillet 2016 13:54
> *À :* softwires@ietf.org
> *Objet :* [Softwires] Fwd: New Version Notification for
> draft-ietf-softwire-map-radius-07.txt
>
>
>
> Hi all,
>
>
>
> We've submitted a new version of draft-ietf-softwire-map-radius
> (version-07) according to comments from the mailing list.
>
>
>
> The main changes are listed below:
>
>
>
> 1. Changed draft title to "RADIUS Attribute for Softwire"
>
> [Med] This title may be misleading given that DS-Lite RADIUS attributes
> are not defined in this document but in RFC6519. Please consider adding a
> note to describe the scope of the document (that is “softwire – dslite”).
>
>
>
TX>Currently, the text in the draft states that it covers only Map-T,
Map-E, and Lightweigfht 4over6. I guess we could add some additional text
to avoid the confusion caused by the title, and a reference to DS-Lite
RADIUS if necessary.


> 2. Separated the use of terms MAP and S46
>
> 3. Numbered the messages in Figure 1 and numbered the supporting text
>
> 4. Removed Figure 2 in section 3 and added text explaining the difference
>
> 5. Removed text about caching of S46 configuration on BNG from section 3
>
> 6. Added a table in section 4.5 showing the valid combination of sub
> options supplied for each Softwire mechanism
>
> 7. Added reference to RFC7678 in section 7 Diameter Considerations
>
>
>
> We really appreciate your comments.
>
> [Med] I have two comments:
>
> * I reiterate my request to include multicast-related attributes into the
> document.
>

TX>I think we'll need consensus from the working group on this matter. If
the working group is in favor of adding multicast-related attributes into
the document, we could merge it in the next version update.


> * The format/specification of the attributes should adhere to RFC6929 and
> https://tools.ietf.org/html/draft-ietf-radext-datatypes-04#section-2.
>
>
>
TX>Thank you for the suggestion, we'll check the attribute format in
accordance to these documents respectively.


> Thanks,
>
> Tianxiang
>
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: 2016-07-07 19:21 GMT+08:00
> Subject: New Version Notification for draft-ietf-softwire-map-radius-07.txt
> To: Bing Liu <leo.liubing@huawei.com>om>, Sheng Jiang <jiangsheng@huawei.com>om>,
> Peter Deacon <peterd@iea-software.com>om>, Yu Fu <fuyu@cnnic.cn>cn>, Tianxiang
> Li <peter416733@gmail.com>om>, Chongfeng Xie <xiechf@ctbri.com.cn>
>
>
>
> A new version of I-D, draft-ietf-softwire-map-radius-07.txt
> has been successfully submitted by Tianxiang Li and posted to the
> IETF repository.
>
> Name:           draft-ietf-softwire-map-radius
> Revision:       07
> Title:          RADIUS Attribute for Softwire
> Document date:  2016-07-07
> Group:          softwire
> Pages:          19
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-softwire-map-radius-07.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/
> Htmlized:
> https://tools.ietf.org/html/draft-ietf-softwire-map-radius-07
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-radius-07
>
> Abstract:
>    IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6
>    connectivity services simultaneously during the IPv4/IPv6 co-existing
>    period.  The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
>    options have been defined to configure Customer Edge (CE) in MAP-E,
>    MAP-T, and Lightweight 4over6.  However, in many networks, the
>    configuration information may be stored in Authentication
>    Authorization and Accounting (AAA) servers while user configuration
>    is mainly from Broadband Network Gateway (BNG) through DHCPv6
>    protocol.  This document defines a Remote Authentication Dial In User
>    Service (RADIUS) attribute that carries CE configuration information
>    from AAA server to BNG.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
>
>