Re: [v6ops] WGLC: draft-ietf-v6ops-nat64-deployment-04

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 09 May 2019 07:53 UTC

Return-Path: <swmike@swm.pp.se>
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 C086612008C; Thu, 9 May 2019 00:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 Urq_okOIx8rb; Thu, 9 May 2019 00:53:09 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F23412011A; Thu, 9 May 2019 00:53:09 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 8C39BB7; Thu, 9 May 2019 09:53:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1557388387; bh=/hWDAeWCa5tfsiNHP7bGvBreaZKycDrW6MFSW5WVrKM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=kYwsTBGHolHoYnSruUBC48vdhgn7et1nRSbaciVRs47+0okHXFDTuGNz8Rk0pkQB3 dn3USQdJlHz2eo6xEYyEhCQYAMSYzZDY1JBtm+WuH6VtlicMhLifWnz8iAPFvrt7yf 3tNkywcoFqNZgxSOzIH69EidkPB/vg6YIeAnmNJ0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 885D7B2; Thu, 9 May 2019 09:53:07 +0200 (CEST)
Date: Thu, 09 May 2019 09:53:07 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-nat64-deployment@ietf.org" <draft-ietf-v6ops-nat64-deployment@ietf.org>
In-Reply-To: <BN7PR05MB424306BDD5C9F07772FEE623AE220@BN7PR05MB4243.namprd05.prod.outlook.com>
Message-ID: <alpine.DEB.2.20.1905090933110.1824@uplift.swm.pp.se>
References: <BYAPR05MB42452273D454F9D3A113ABE6AE2C0@BYAPR05MB4245.namprd05.prod.outlook.com> <BN7PR05MB424306BDD5C9F07772FEE623AE220@BN7PR05MB4243.namprd05.prod.outlook.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/bq_1YdqGg4s4dBDTl3K4egSkpiM>
Subject: Re: [v6ops] WGLC: draft-ietf-v6ops-nat64-deployment-04
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 09 May 2019 07:53:12 -0000

On Mon, 22 Apr 2019, Ron Bonica wrote:

> Folks,
>
> This ends WG Last Call on draft-ietf-v6ops-nat64-deployment-04.
>
> Mikael,
>
> Would you provide the shepherd's write-up.

As part of this write-up I realised RFC2119/RFC8174 language in there, is 
this really applicable for this kind of draft? Do we need more text on 
what this really means?

Can an informational draft even use RFC2119/RFC8174 language in it with 
the boilerplate RFC8174 header? RFC7084 is informational but has a 
different RFC2119/8174 reference section that spells out what it means 
when it's using this language.

There are things like:

"Taking in consideration that discussion and other issues, we can
    summarize the possible decision points as:

    a.  The WKP MUST NOT be used to represent non-global IPv4 addresses.
        If this is required because the network to be translated use non-
        global addresses, then an NSP is required."

So first there is some kind of considerations/summary list and then we get 
RFC2119 language?

Also, the lists in the document are either as 1,2,3 or a,b,c or bullet 
lists with "o" before. Is there a difference between these different 
methods of "numbering" lists?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se