Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00

Arturo Servin <aservin@lacnic.net> Wed, 14 August 2013 16:15 UTC

Return-Path: <aservin@lacnic.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B90D21E808C for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2013 09:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOdvTiVy13pj for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2013 09:15:54 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 17D9321F9B12 for <v6ops@ietf.org>; Wed, 14 Aug 2013 09:15:47 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:7000:fc91:b334:be1e:5ce9]) by mail.lacnic.net.uy (Postfix) with ESMTP id 8BDCA308432 for <v6ops@ietf.org>; Wed, 14 Aug 2013 13:15:21 -0300 (UYT)
Message-ID: <520BAD34.1080903@lacnic.net>
Date: Wed, 14 Aug 2013 13:15:48 -0300
From: Arturo Servin <aservin@lacnic.net>
Organization: LACNIC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: v6ops@ietf.org
References: <5207D42F.2030302@nic.br> <5207E319.6070601@nic.br> <8C48B86A895913448548E6D15DA7553B97DA03@xmb-rcd-x09.cisco.com> <CA+z-_EWFAGFqyo3E3LzrEhpMRV6axdLJTC50BNwXMNGuJtZuTA@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230439ABEFA4@PRVPEXVS15.corp.twcable.com> <A84D9405-B3D2-4D55-BAEE-FE25ACE45EB6@delong.com> <2671C6CDFBB59E47B64C10B3E0BD59230439ABF00C@PRVPEXVS15.corp.twcable.com> <7E5164F5-CB38-49D1-94F5-5125FCD2416E@delong.com> <52095DAF.2050505@nic.br> <2671C6CDFBB59E47B64C10B3E0BD59230439ABF61A@PRVPEXVS15.corp.twcable.com> <4910BB30-FF77-4E69-8B60-E35E5847DB2F@delong.com> <2671C6CDFBB59E47B64C10B3E0BD59230439ABF936@PRVPEXVS15.corp.twcable.com> <520AD94F.1050604@nic.br> <1376445275.5223.YahooMailNeo@web142501.mail.bf1.yahoo.com> <520B029C.3010308@nic.br> <2671C6CDFBB59E47B64C10B3E0BD59230439B6F9C3@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230439B6F9C3@PRVPEXVS15.corp.twcable.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Subject: Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 14 Aug 2013 16:15:55 -0000

>>>> Yes, we could use a
>>>> /32 from ULA space, instead of from GLA space. But we think it would
>>>> generate confusion.
>>>>
>>>> I think we are not really talking about impossibilities, but about
>>>> options. We are talking about to write documents easier to read, labs
>>>> easier to understand.
>>>>
>>>> In some situations, for teaching, or writing scripts for labs,
>> howtos,
>>>
>>>> books, brochures, etc, it's better, simpler, easier, more precise,
>> more
>>>> clear, to use a prefix shorter than /32. In some situations we are
>> doing
>>>> that, and we have seen other groups doing the same.
>>>>
> [WEG] I think over the course of this discussion, you've built a reasonable case for this with real-world examples to back up your assertions. However, just as teachers like you to show your work when solving a math problem, I strongly suggest that you revise the draft to include this supporting information in order to build the case, else you'll have this conversation every time someone reads the draft and is skeptical that more space is needed. I realize that 3849 is light on justification and you patterned this draft after that document, but few would argue that at least one prefix for documentation is necessary and appropriate. As you've seen, fewer are convinced that additional prefixes or larger prefixes are needed without some background information from those with experience in training and documentation that have observed some real-world problems with the current solution. I can't guarantee that you won't have more "you're doing it wrong" arguments, but at least yo
 u'
>  re demonstrating that it's not an arbitrary request.
> 
> Wes George
> 

	Thank Wes, very valuable input.

Regards,
as