IETF Logo Mail Archive

Re: [sunset4] Mandating use of IPv6 in examples

"Joel Bion (jpbion)" <jpbion@cisco.com> Wed, 06 April 2016 14:38 UTC

Return-Path: <jpbion@cisco.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC48312D15F for <sunset4@ietfa.amsl.com>; Wed, 6 Apr 2016 07:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 sXCIV_JleZqh for <sunset4@ietfa.amsl.com>; Wed, 6 Apr 2016 07:38:02 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4F6C12D1E4 for <sunset4@ietf.org>; Wed, 6 Apr 2016 07:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4503; q=dns/txt; s=iport; t=1459953478; x=1461163078; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=y2US4GinWrjMM0titroTDozVSt6UybRi9xn89zUs4Kw=; b=jySJLD275eCGusiXypiS09/Fyw6rWZolvJxOxcGVQrCclcNc60SpWyCX GoTXqT1tNsqqOA07RPpL9BF8bTAv0zalNxk7dZZ4MZBQWq9vZkfyW6bD8 xqB3jgsYzNvR3dGBTs7ofCNQVwvIJ/bXC1ye50TZmN0xvi0isvxCks4O5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAgCgHgVX/5tdJa1cgzdTfYVGqS6LVwENgXIXAQmEFYENSgKBSDgUAQEBAQEBAWUnhEIBAQQBAQFrCxACAQgEOwchBgsUEQIEDgWIEgMSDrtXDYR8AQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSIFoJWgkGCK4J+gisFl1AxAYwVgXWPDodHh1kBHgEBQoFMghtsiHMBAQE
X-IronPort-AV: E=Sophos;i="5.24,447,1454976000"; d="scan'208,217";a="258033540"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2016 14:37:57 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u36EbvW8022219 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 6 Apr 2016 14:37:57 GMT
Received: from xch-rcd-020.cisco.com (173.37.102.30) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 6 Apr 2016 09:37:56 -0500
Received: from xch-rcd-020.cisco.com ([173.37.102.30]) by XCH-RCD-020.cisco.com ([173.37.102.30]) with mapi id 15.00.1104.009; Wed, 6 Apr 2016 09:37:56 -0500
From: "Joel Bion (jpbion)" <jpbion@cisco.com>
To: Erik Nygren <erik+ietf@nygren.org>
Thread-Topic: [sunset4] Mandating use of IPv6 in examples
Thread-Index: AQHRj/r3cEI0KtbylEuxPLxyAtJnY599OFKAgAAHMICAAAmcAIAACmaA//+wV68=
Date: Wed, 06 Apr 2016 14:37:56 +0000
Message-ID: <565EB659-02A0-4E86-8B46-FA00D6291016@cisco.com>
References: <5704F8BA.20400@gmail.com> <570504F7.1030708@gmail.com> <CCFC5474-3773-4D43-BA66-DC6D06AE3E26@consulintel.es> <CALo9H1bDsQXmq6YYMwFyOhYt-tWs+F_4SzUAb7pAzh83+D4sig@mail.gmail.com>, <CAKC-DJjYGbaFGhtS+rxBdWfJan3-bCucKF+Op5-sqNxCb1tXNg@mail.gmail.com>
In-Reply-To: <CAKC-DJjYGbaFGhtS+rxBdWfJan3-bCucKF+Op5-sqNxCb1tXNg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_565EB65902A04E868B46FA00D6291016ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sunset4/-qBZtXqPWxmRCAhPQvkQ9qgLhsg>
Cc: Arturo Servin <arturo.servin@gmail.com>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "sunset4@ietf.org" <sunset4@ietf.org>
Subject: Re: [sunset4] Mandating use of IPv6 in examples
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 14:38:07 -0000

Maybe because in doing so they show they can actually think natively with IPv6 addresses? (You'd perhaps be surprised by the number of people I run into even today who treat each v6 address like it's something they have to send through  a translator to understand).

Sent from my iPhone

On Apr 6, 2016, at 7:23 AM, Erik Nygren <erik+ietf@nygren.org<mailto:erik+ietf@nygren.org>> wrote:

+1

This seems worthwhile.  Anecdotally, I've seen that engineering teams which include IPv6 examples in their design docs
(eg, showing sample configurations or sample config screens or test case examples) seem much more likely
to properly implement and test IPv6 support as a first-class feature.

   Erik



On Wed, Apr 6, 2016 at 10:45 AM, Arturo Servin <arturo.servin@gmail.com<mailto:arturo.servin@gmail.com>> wrote:

>I recently submitted an I-D
>draft-robachevsky-mandating-use-of-ipv6-examples-00.txt, mandating use
>of IPv6 in examples in RFCs.
>
>I was reading some pretty recent drafts and noticed that authors
>continue using IPv4 in their examples. This is probably more convenient,
>but is not really forward thinking. Also, the prevalence of IPv6
>examples will send a strong message that IPv4 is essentially a legacy
>protocol.
_______________________________________________
sunset4 mailing list
sunset4@ietf.org<mailto:sunset4@ietf.org>
https://www.ietf.org/mailman/listinfo/sunset4

v2.46.0 | Report a Bug | By Email | System Status