Re: [v6ops] Inviting discussion: draft-liu-v6ops-running-multiple-prefixes

Sheng Jiang <jiangsheng@huawei.com> Mon, 02 March 2015 07:16 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6FE1A1A66 for <v6ops@ietfa.amsl.com>; Sun, 1 Mar 2015 23:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 8dFtzjWwY4V2 for <v6ops@ietfa.amsl.com>; Sun, 1 Mar 2015 23:16:56 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 611761A004A for <v6ops@ietf.org>; Sun, 1 Mar 2015 23:16:56 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPT64706; Mon, 02 Mar 2015 07:16:54 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Mar 2015 07:16:53 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Mon, 2 Mar 2015 15:16:44 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Inviting discussion: draft-liu-v6ops-running-multiple-prefixes
Thread-Index: AQHQT8u8J8lmkJBw0E60yhTq/eTBy50IzY4g
Date: Mon, 2 Mar 2015 07:16:43 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923B053D24@nkgeml512-mbx.china.huawei.com>
References: <8C48B86A895913448548E6D15DA7553B0612B394@xmb-rcd-x09.cisco.com> <54EBCA81.30301@gmail.com>
In-Reply-To: <54EBCA81.30301@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/9sEhBxwSd-EaXcuz_ox1iQbnZGM>
Subject: Re: [v6ops] Inviting discussion: draft-liu-v6ops-running-multiple-prefixes
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2015 07:16:58 -0000

>On 20/02/2015 09:54, Fred Baker (fred) wrote:
>> https://tools.ietf.org/html/draft-liu-v6ops-running-multiple-prefixes
>>   "Considerations for Running Multiple IPv6 Prefixes", Bing Liu, Sheng
>>   Jiang, Yang Bo, 2014-10-11,
>>
>> This draft was prepared for IETF 91, but didn't get discussed in part because
>>a number of Chinese participants didn't make it to Honolulu for a Monday
>>meeting. Is there interest in discussing it at IETF 92?
>
>I think we should discuss whether the WG wants to publish
>a background document on this topic. This is one of the aspects
>of v6 that seems to be quite unexpected by current operators
>of site networks. Educating them seems desirable.

Giving this is a major differentia from IPv4 and many operators would have problems without knowing 

>The only thing
>is, this really is only a background document, not a "how to"
>guide

I guess this is a direction that the current document should be improved toward. It was created as a mixture of background information, "how-to" for operators and "problems" for standard actions. Focusing on background would give the document much clearer purpose.

>- and it cites 7 I-Ds, which isn't ideal for an informational
>document. Will it help those operators, or will they throw it
>on the "too hard" heap?

Most of these I-Ds are "problems" for standard actions. They are on their own progresses. Since we want to focus on background only, these I-Ds would be removed certainly.

>So, if we give it agenda time, I suggest we discuss the purpose
>of the document, not its details.

Good advice. We will follow. Thanks.

Best regards,

Sheng

>     Brian
>
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops