Re: [v6ops] Checking an outcome on the list
"Dave Michaud" <Dave.Michaud@rci.rogers.com> Fri, 08 November 2013 17:44 UTC
Return-Path: <prvs=017fb8179=Dave.Michaud@rci.rogers.com>
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 149DD21E81D1 for <v6ops@ietfa.amsl.com>; Fri, 8 Nov 2013 09:44:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.665
X-Spam-Level:
X-Spam-Status: No, score=0.665 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_50=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqH0Xw3zCGDM for <v6ops@ietfa.amsl.com>; Fri, 8 Nov 2013 09:44:47 -0800 (PST)
Received: from mail.mail.rss.rogers.com (mail.mail.rss.rogers.com [142.146.31.23]) by ietfa.amsl.com (Postfix) with ESMTP id 1A89521E8189 for <v6ops@ietf.org>; Fri, 8 Nov 2013 09:44:47 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAPshfVKOkg56l2dsb2JhbABZwyiBRg4BAQEBAQgWBzyCJQEBAQMBEh4KGQsBBgkQBwYBCBEEAQELBhcBB0UJCgQBEggRAgeHWQafGp4PjzY+gxqBEAOJQoVankIe
X-IronPort-AV: E=Sophos;i="4.93,661,1378872000"; d="scan'208";a="344432856"
Received: from rssesnexigwb.rss.rogers.com (HELO rsoesnexigwb.rci.rogers.ca) ([142.146.14.122]) by mail.mail.rss.rogers.com with ESMTP; 08 Nov 2013 12:44:34 -0500
Received: from RSOESNGTABHC.rci.rogers.ca ([10.3.37.54]) by rsoesnexigwb.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675); Fri, 8 Nov 2013 12:44:34 -0500
Received: from CL08MBE.rci.rogers.ca ([10.3.45.56]) by RSOESNGTABHC.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675); Fri, 8 Nov 2013 12:44:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 08 Nov 2013 12:44:31 -0500
Message-ID: <29AE8DB910E7704CA043795E00DCBE780AB193BB@CL08MBE.rci.rogers.ca>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Checking an outcome on the list
Thread-Index: AQHO3Aype5QzVdxtfEaHGp2VxesyKZobmISA
From: Dave Michaud <Dave.Michaud@rci.rogers.com>
To: "Fred Baker (fred)" <fred@cisco.com>, v6ops@ietf.org
X-OriginalArrivalTime: 08 Nov 2013 17:44:34.0599 (UTC) FILETIME=[2FDE9370:01CEDCAA]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: Re: [v6ops] Checking an outcome on the list
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 08 Nov 2013 17:44:57 -0000
Comments are inline Dave Michaud > -----Original Message----- > From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of > Fred Baker (fred) > Sent: Thursday, November 07, 2013 2:57 PM > To: v6ops@ietf.org WG > Subject: [v6ops] Checking an outcome on the list > > We say we check f2f decisions on the mailing list to ensure that everyone had a > chance to speak. Let's do that. > > In IETF 88, we discussed a number of drafts. Of these: > - draft-ietf-v6ops-balanced-ipv6-security will start a two week WGLC on > Monday morning New Zealand time. Ok > - draft-ietf-v6ops-nat64-experience appears to have reached closure. We have > one additional revision coming, and then will do a 1 week last call, probably > early December. I will review once the final version is in. > - draft-liu-bonica-v6ops-dhcpv6-slaac-problem documents what seems to be a > real problem. > 1) In your opinion, should draft-liu-bonica-v6ops-dhcpv6-slaac-problem be > adopted as WG draft draft-ietf-v6ops-dhcpv6-slaac-problem and matured into a > problem statement to present to 6man? Yes > 2) In your opinion, should v6ops invite a draft (which we might adopt as a > working group draft) that gives current guidance to operators regarding the > use of DHCP and SLAAC in their networks? Yes > - Should draft-chen-v6ops-ipv6-roaming-analysis be adopted as WG draft > draft-ietf-v6ops-ipv6-roaming-analysis? 3GPP specifies how the cellular nodes SHOULD behave GSMA specifies provides guidelines on how operators SHOULD configure roaming IETF v6ops (through this draft) presents a real life view of what challenges/issues operators will face with IPv6 roaming It is in the best interest for the advancement of Mobile IPv6 deployment to have as much information as possible on the potential impacts and potential solutions that operators will face when enabling IPv6 roaming. I therefore support that this draft is adopted as a WG draft. > > I'll collect up the responses in a week and make a determination based on that. > I'm interested in your viewpoint, whether positive or negative. If you would > prefer to send it privately to v6ops-chairs@tools.ietf.org, that works too. This e-mail (and attachment(s)) is confidential, proprietary, may be subject to copyright and legal privilege and no related rights are waived. If you are not the intended recipient or its agent, any review, dissemination, distribution or copying of this e-mail or any of its content is strictly prohibited and may be unlawful. All messages may be monitored as permitted by applicable law and regulations and our policies to protect our business. E-mails are not secure and you are deemed to have accepted any risk if you communicate with us by e-mail. If received in error, please notify us immediately and delete the e-mail (and any attachments) from any computer or any storage medium without printing a copy. Ce courriel (ainsi que ses pièces jointes) est confidentiel, exclusif, et peut faire l’objet de droit d’auteur et de privilège juridique; aucun droit connexe n’est exclu. Si vous n’êtes pas le destinataire visé ou son représentant, toute étude, diffusion, transmission ou copie de ce courriel en tout ou en partie, est strictement interdite et peut être illégale. Tous les messages peuvent être surveillés, selon les lois et règlements applicables et les politiques de protection de notre entreprise. Les courriels ne sont pas sécurisés et vous êtes réputés avoir accepté tous les risques qui y sont liés si vous choisissez de communiquer avec nous par ce moyen. Si vous avez reçu ce message par erreur, veuillez nous en aviser immédiatement et supprimer ce courriel (ainsi que toutes ses pièces jointes) de tout ordinateur ou support de données sans en imprimer une copie.
- Re: [v6ops] Checking an outcome on the list Brian E Carpenter
- [v6ops] Checking an outcome on the list Fred Baker (fred)
- Re: [v6ops] Checking an outcome on the list Mikael Abrahamsson
- Re: [v6ops] Checking an outcome on the list Cong Liu
- Re: [v6ops] Checking an outcome on the list Dave Michaud
- Re: [v6ops] Checking an outcome on the list Sheng Jiang
- Re: [v6ops] Checking an outcome on the list Alexandru Petrescu
- Re: [v6ops] Checking an outcome on the list Hui Deng
- Re: [v6ops] Checking an outcome on the list Ida Leung
- Re: [v6ops] draft-chen-v6ops-ipv6-roaming (was: C… Alexandru Petrescu
- Re: [v6ops] draft-chen-v6ops-ipv6-roaming Tore Anderson