Re: [v6ops] comments on draft-ietf-v6ops-rfc7084-bis-02

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 12 June 2017 13:14 UTC

Return-Path: <prvs=1336cd027b=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 C93B6129515 for <v6ops@ietfa.amsl.com>; Mon, 12 Jun 2017 06:14:37 -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 oZXWaXZw0EdC for <v6ops@ietfa.amsl.com>; Mon, 12 Jun 2017 06:14:35 -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 1AC871205F1 for <v6ops@ietf.org>; Mon, 12 Jun 2017 06:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1497273273; x=1497878073; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=8Lr9GfWQFAdXfjP2TKzRkK9ld Bee/w/lU7fAY8XW6Z8=; b=ZiUVbHuVUhYoX6gIbqkpW2NcFrvcjAFOUrjv29OIv Ix2CtQJhvxhYqwKYyVDc+E0vhDrxHhzn4LXW69Uw8xiNg0ymOd0AlpqNx6v020LJ 6458wk3OZKvrOdTCEkpo+79B2SGcBO61pMuEHEfwRzW7qujVGLiIiqHhtTkqIANS r4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=nP4BgR672wFJtsqoK7NvEtofIaCXCcutnfit746+Oswir7/XaBi4VyKQ28Ko MvRiLbepbo9XTuFMcqNKHcIuarOvSiyl2k+MSiVX4bubYkQ+ip5/HcL03 u9FGOEOxetCBI2vJCiKfsOu0fjRbd3zK4kQAJpn9Fqlavj5fd6I8b0=;
X-MDAV-Processed: mail.consulintel.es, Mon, 12 Jun 2017 15:14:33 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 12 Jun 2017 15:14:32 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005449514.msg for <v6ops@ietf.org>; Mon, 12 Jun 2017 15:14:31 +0200
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:170612:md50005449514::ppcFzARSGLr9vA2j:00003dp6
X-Return-Path: prvs=1336cd027b=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Mon, 12 Jun 2017 15:14:26 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <CDDB904E-065C-4398-99D7-AC848F59FCEA@consulintel.es>
Thread-Topic: [v6ops] comments on draft-ietf-v6ops-rfc7084-bis-02
References: <5DDD9835-86D9-41AF-951E-F2FF7C281926@consulintel.es> <2D09D61DDFA73D4C884805CC7865E6114DB879D0@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DB879D0@GAALPA1MSGUSRBF.ITServices.sbc.com>
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/tk6-BvC-VPA8P2ekwW8XJvAcFuM>
Subject: Re: [v6ops] comments on draft-ietf-v6ops-rfc7084-bis-02
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: Mon, 12 Jun 2017 13:14:38 -0000

Hi Barbara,

Agree, I was not considering dropping RFC7083 at all.

In RFC7084-bis I conserved the "optional" language status for the transition, so I still think this is the correct way forward. Despite that, I think if you look to either

1) https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc7084-bis2/?include_text=1

or

2) https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc7084-bis4-hncp/?include_text=1

You will be fine, as in both cases transition support has been completely removed and that will be a separated document.

Difference among both of them:

1) Is an “IPv6-only” CE, very minimalistic approach, for simple networks, may be even “smaller” ones that a home network.
2) Is an IPv6 CE, “dual-stack” support, including HNCP.

Somehow both of them are in the “middle way” between 6204 and 7084.

Of course, other combinations are possible … 

Regards,
Jordi
 

-----Mensaje original-----
De: "STARK, BARBARA H" <bs7652@att.com>
Responder a: <bs7652@att.com>
Fecha: lunes, 12 de junio de 2017, 15:02
Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "v6ops@ietf.org" <v6ops@ietf.org>
Asunto: RE: [v6ops] comments on draft-ietf-v6ops-rfc7084-bis-02

    > Basically, we need to go back to RFC6204 (which didn’t included transition at
    > all) and even more NOT include IPv4 support at all
    
    RFC 7084 added requirements for MAX SOL RT (RFC 7083) to RFC 6204. In fact, this one requirement was responsible for delaying publication of RFC 7084 by almost a year. It was such an important requirement that everyone agreed it was better to wait for this than to publish without it.
    There were also a few other changes to RFC 6204 requirements, but that was by far the most important and most needed. 
    Therefore, I do not support reverting to RFC 6204. 
    When Hans Liu was distinguishing between support for RFC 6204 and RFC 7084, I'm hoping he didn't mean that CE Router vendors aren't supporting MAX SOL RT. I think MAX SOL RT did get added to the UNH-IOL IPv6 Ready CE Router tests. I'm hoping he just meant that many CE Routers don't support any transition technologies.
    
    The "Transition Technologies Support" section that was added was done with purely "optional" language. There is not a single mandatory transition technology in RFC 7084. A CE Router can be 100% compliant with RFC 7084 and support no transition technologies.
    
    I'm perfectly happy with pulling the entire "Transition Technologies Support" section out of a RFC 7084-bis.
    Barbara
    



**********************************************
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.