Re: [v6ops] draft-ietf-v6ops-6204bis WGLC

"Ralph Droms (rdroms)" <rdroms@cisco.com> Sat, 24 March 2012 11:40 UTC

Return-Path: <rdroms@cisco.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 7573321F8716 for <v6ops@ietfa.amsl.com>; Sat, 24 Mar 2012 04:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.449
X-Spam-Level:
X-Spam-Status: No, score=-8.449 tagged_above=-999 required=5 tests=[AWL=-0.517, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 Nkf9V4NNRPVb for <v6ops@ietfa.amsl.com>; Sat, 24 Mar 2012 04:40:20 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0C621F870F for <v6ops@ietf.org>; Sat, 24 Mar 2012 04:40:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rdroms@cisco.com; l=3026; q=dns/txt; s=iport; t=1332589220; x=1333798820; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=0iqvYXSb3TaWOXmJh7YsFF8q8xrv5pvq95nzObyonzQ=; b=LsTx8xvsduK6oR0rNLdLQovnAAggsDXU6zF78wjpp7VfxxIDys4JbIM9 SlEESdtNeGyrSCXfEfS+fVYGged9dEUHRhYSg7fb6Q4RLX4Ne2Hba34Iy K6UJbb877nCiKWUbrgZoe8bNd0ZvUHuZ2MJmYS7bDatFcv6MqBdc5F+iz w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMJAISxbU+tJV2a/2dsb2JhbABEhT+xYX4CgQeCCQEBAQMBAQEBDwEQEToLEAIBCBgCAiYCAgIlMAEBBBMih2MFC5lVjQiRVwSBL45hNWMElWCORYFogmiBWw
X-IronPort-AV: E=Sophos;i="4.73,641,1325462400"; d="scan'208";a="69096607"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 24 Mar 2012 11:40:20 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q2OBeKZt001412; Sat, 24 Mar 2012 11:40:20 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 24 Mar 2012 06:40:19 -0500
Received: from 72.163.43.39 ([72.163.43.39]) by XMB-RCD-202.cisco.com ([72.163.62.209]) with Microsoft Exchange Server HTTP-DAV ; Sat, 24 Mar 2012 11:40:19 +0000
References: <6A0BFABB-225C-4D14-83F5-4398AF0E5CC3@cisco.com> <A2297077-2804-407E-9971-5459F0E39806@townsley.net> <5B6B2B64C9FE2A489045EEEADDAFF2C30444B2D2@XMB-RCD-109.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30444B2E1@XMB-RCD-109.cisco.com> <3723BC44-931F-4852-88A4-716931770F85@cisco.com> <B5D87268-1B10-41D8-9948-650AFDD0B657@cisco.com> <D0CE7E85-CEA6-470D-A388-0C9A56C3E77B@townsley.net>
Content-Transfer-Encoding: base64
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Content-Type: text/plain; charset="utf-8"
Thread-Topic: [v6ops] draft-ietf-v6ops-6204bis WGLC
Thread-Index: Ac0JsuPR2glI91MtR1mRuqvCEr/a5g==
In-Reply-To: <D0CE7E85-CEA6-470D-A388-0C9A56C3E77B@townsley.net>
Message-ID: <2131186D-4C82-418A-A359-C568F78CD19B@cisco.com>
Date: Sat, 24 Mar 2012 12:40:13 +0100
To: Mark Townsley <mark@townsley.net>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 24 Mar 2012 11:40:19.0748 (UTC) FILETIME=[E3FD7640:01CD09B2]
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6204bis WGLC
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: Sat, 24 Mar 2012 11:40:21 -0000




On Mar 24, 2012, at 12:33 PM, "Mark Townsley" <mark@townsley.net> wrote:

> 
> On Mar 24, 2012, at 12:26 PM, Ralph Droms (rdroms) wrote:
> 
>> it's way too nice a day to give the issue the consideration it deserves.   
> 
> Enjoy Spring in Paris, Ralph. Wish I was :-)

The weather is a little better than when I was here for the IPv6 World Congress...

> 
>> So, I'll post a response, but likely not until tomorrow when I'll be sequestered indoors most of the day, anyway.
> 
> FWIW, it seem the chairs have given airtime for us to talk about this Monday morning if you want to wait until you have heard the real-time part of the discussion.

Why do I need to hear all the data before giving an opinion?

- Ralph

> 
> - Mark
> 
> 
>> 
>> - Ralph
>> 
>> On Mar 24, 2012, at 12:17 PM, "Fred Baker" <fred@cisco.com> wrote:
>> 
>>> 
>>> On Mar 24, 2012, at 10:31 AM, Hemant Singh (shemant) wrote:
>>> 
>>>> Further, isn’t draft-townsley-troan-ipv6-ce-transitioning-02 specifying technology or is there another document that covers the technology in more detail?  Technology documents need to move to a different WG. 
>>> 
>>> I'm reading your statement above, and in other email reading statements by someone using the same email address that go into some detail on the implications of binary flags in messages. I'm wondering where the line is drawn and why one draws it.
>>> 
>>> I have asked a selection of ADs and WG Chairs to weigh in on where the document should be discussed; if someone comes back to Joel and I with "this obviously belongs in <>", we'll send it there or send the relevant subset there. Personally, I think it falls within the charter of operational procedures used in IPv6 networks.
>>> 
>>> Where I draw the line on the normative reference that Ole and Mark would like is how well baked the proposed procedures are. We will determine that Monday.
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>