IETF Logo Mail Archive

Re: [sunset4] IP on draft-ietf-sunset4-ipv6-ietf

Jacques Latour <Jacques.Latour@cira.ca> Tue, 19 September 2017 13:54 UTC

Return-Path: <Jacques.Latour@cira.ca>
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 C079C134328; Tue, 19 Sep 2017 06:54:32 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IeixRRrQYLdX; Tue, 19 Sep 2017 06:54:31 -0700 (PDT)
Received: from mx2.cira.ca (mx2.cira.ca [192.228.22.117]) by ietfa.amsl.com (Postfix) with ESMTP id 576C4134322; Tue, 19 Sep 2017 06:54:28 -0700 (PDT)
X-Virus-Scanned: by SpamTitan at corp.cira.ca
Received: from CRP-EX16-02.CORP.CIRA.CA (10.2.36.121) by CRP-EX16-01.CORP.CIRA.CA (10.2.36.120) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Tue, 19 Sep 2017 09:54:27 -0400
Received: from CRP-EX16-02.CORP.CIRA.CA ([fe80::15c6:1482:4083:e9f7]) by CRP-EX16-02.CORP.CIRA.CA ([fe80::15c6:1482:4083:e9f7%13]) with mapi id 15.01.0669.032; Tue, 19 Sep 2017 09:54:27 -0400
From: Jacques Latour <Jacques.Latour@cira.ca>
To: Lee Howard <lee@asgard.org>, MarcBlanchet <marc.blanchet@viagenie.ca>
CC: "draft-ietf-sunset4-ipv6-ietf@ietf.org" <draft-ietf-sunset4-ipv6-ietf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
Thread-Topic: [sunset4] IP on draft-ietf-sunset4-ipv6-ietf
Thread-Index: AQHTMT/5ik1Bx/Ti2UafREeRRrI6X6K8eTgA//+/8uA=
Date: Tue, 19 Sep 2017 13:54:27 +0000
Message-ID: <ad25cb260d8c4031b94dfb7eefdae918@cira.ca>
References: <A2FA7C51-3326-485D-A3F7-2FEE8B3EC521@viagenie.ca> <379DC2F9-4553-472B-88EC-56A1AE47D214@asgard.org>
In-Reply-To: <379DC2F9-4553-472B-88EC-56A1AE47D214@asgard.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.4.166]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/1mFgCYyr7rj8dtUrKGfIeU2JAiw>
Subject: Re: [sunset4] IP on draft-ietf-sunset4-ipv6-ietf
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 19 Sep 2017 13:54:33 -0000

Hi,

I know I'm late on the reviewing part, but just wondering how the policing part will work, who will ensure the "IETF work will explicitly support IPv6" activities?

Second, as an example, when this come in effect, would this draft "https://tools.ietf.org/html/draft-ietf-nvo3-mcast-framework-09" specifically exclude IPv4 specifications, meaning this new framework work should only be applied to IPv6, and ideally make IPv6 feature rich vs. IPv4.

Jacques


-----Original Message-----
From: sunset4 [mailto:sunset4-bounces@ietf.org] On Behalf Of Lee Howard
Sent: September 19, 2017 9:37 AM
To: MarcBlanchet <marc.blanchet@viagenie.ca>
Cc: draft-ietf-sunset4-ipv6-ietf@ietf.org; sunset4@ietf.org
Subject: Re: [sunset4] IP on draft-ietf-sunset4-ipv6-ietf

Lol 
I know of no IPR related to this draft. 

Lee

Sent from my iPhone

> On Sep 19, 2017, at 8:08 AM, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:
> 
> Dear author,
> please state if you have direct, personal knowledge of any IPR related to this document (draft-ietf-sunset4-ipv6-ietf), and if yes, was it disclosed, in conformance with BCPs 78 and 79.
> 
> Regards, Marc, document shepherd
> 
> _______________________________________________
> sunset4 mailing list
> sunset4@ietf.org
> https://www.ietf.org/mailman/listinfo/sunset4
> 

_______________________________________________
sunset4 mailing list
sunset4@ietf.org
https://www.ietf.org/mailman/listinfo/sunset4

v2.23.0 | Report a Bug | By Email