IETF Logo Mail Archive

Re: [v6ops] Comments on draft-palet-v6ops-rfc7084-bis-01

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 22 March 2017 22:08 UTC

Return-Path: <prvs=12549852b0=jordi.palet@consulintel.es>
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 5E045129BC7 for <v6ops@ietfa.amsl.com>; Wed, 22 Mar 2017 15:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 1hvAOmk3SK0n for <v6ops@ietfa.amsl.com>; Wed, 22 Mar 2017 15:08:49 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D32C1292D3 for <v6ops@ietf.org>; Wed, 22 Mar 2017 15:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1490220527; x=1490825327; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: Mime-version:Content-type:Content-transfer-encoding:Reply-To; bh=rFDx0HOcPQAqSOuBWfuGQ2r6y5fV0VSkDRVyNwRwang=; b=VjGm4WsvI99ZL z6Q5SlfhF+pcan5LPGUVh+Ab/YCVC3yQwHi1scD5NcPIJ0AOUMq5Mqt7MWV/qQtx KgJq1mPvPooSVyOfisZ1hgxqVC237QspqWOBfIjAOpBL2G8vFZ7MX5PBeEXDtk63 jzpHqZfeQh/OuFs+cYA9QuYkITPT6M=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=Mfvt6tcClRf1TKj2SIjEWIWmiLv0i6n6SY6CQY5w7RQxBpvjk9IYCL7ZgeGC QotAx27HAE+6f7HE78mUfsaoB1v+pOOXjgCBjV84kBTv5zVkejYjzm8dJ Y4FSLTWx3ELdcPi7kJJqTBAOjWI7VwNWzPG5AjW2ZrnmigxXMCDw4g=;
X-MDAV-Processed: mail.consulintel.es, Wed, 22 Mar 2017 23:08:47 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 22 Mar 2017 23:08:42 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005393720.msg for <v6ops@ietf.org>; Wed, 22 Mar 2017 23:08:42 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170322:md50005393720::v7bcYHmyyzQjPtnY:00006JGk
X-Return-Path: prvs=12549852b0=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Wed, 22 Mar 2017 23:08:39 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <2096FB08-9995-4BD0-95DE-492DEF949248@consulintel.es>
Thread-Topic: [v6ops] Comments on draft-palet-v6ops-rfc7084-bis-01
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/X47KGXPuzTqHhCnusTET_fGDP-E>
Subject: Re: [v6ops] Comments on draft-palet-v6ops-rfc7084-bis-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Mar 2017 22:08:51 -0000

Hi Ron,

I’ve followed exactly the same wording that was already used in the previous version of this document, and in fact, asked in the mailing list if we want to change some to MAY and others to MUST, etc. I think the conclusion was to keep SHOULD.

I also checked (and reported it in the list) how much takes in the code (which is open source, so nothing “new” to write), to implement one or several of those transitions mechanism, and it was a few Kbytes.

https://www.ietf.org/mail-archive/web/v6ops/current/msg25470.html

Regarding the different market segments, I think I’ve covered that in this message:

https://www.ietf.org/mail-archive/web/v6ops/current/msg25533.html

I’m already working on the slides for Chicago, and I plan to provide some more detail/inputs on both of those topics, so any new inputs are welcome so I can increase the info in the slides if needed.

You may be right, I really don't know if we are % following the 2119, we may want to discuss this if we heard other opinions?

Regards,
Jordi
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Ron Bonica <rbonica@juniper.net>
Responder a: <rbonica@juniper.net>
Fecha: miércoles, 22 de marzo de 2017, 18:00
Para: IPv6 Ops WG <v6ops@ietf.org>
Asunto: [v6ops] Comments on draft-palet-v6ops-rfc7084-bis-01

    Jordi,
    
    Thanks for writing this draft. I have only one comment. 
    
    In a few places, you say that "The CE router SHOULD support foo", where foo might be 464xlat, MAP-E, MAP-T, DS-LITE, etc. I am wondering if this is an appropriate use of the 2119 keyword. 
    
    Are these technologies required, unless there is a good reason not to implement them. If a vendor wants to address one market segment and not another, is sufficient reason not to implement.
    
    
                                                                                       /hatless
                                                                                       Ron
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

v2.23.0 | Report a Bug | By Email