Re: [v6ops] IPV6 Operational and Implementation guide?

Arturo Servin <aservin@lacnic.net> Thu, 11 April 2013 17:22 UTC

Return-Path: <aservin@lacnic.net>
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 E054A21F87B1 for <v6ops@ietfa.amsl.com>; Thu, 11 Apr 2013 10:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 rlcUjqEqqhCU for <v6ops@ietfa.amsl.com>; Thu, 11 Apr 2013 10:22:23 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id DD77421F86F7 for <v6ops@ietf.org>; Thu, 11 Apr 2013 10:22:22 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:7000:95d8:e0af:510:ea86]) by mail.lacnic.net.uy (Postfix) with ESMTP id 82DFB308465 for <v6ops@ietf.org>; Thu, 11 Apr 2013 14:22:01 -0300 (UYT)
Message-ID: <5166F142.8010204@lacnic.net>
Date: Thu, 11 Apr 2013 14:22:10 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: v6ops@ietf.org
References: <4FC37E442D05A748896589E468752CAA0A684528@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0A684528@PWN401EA160.ent.corp.bcbsm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Subject: Re: [v6ops] IPV6 Operational and Implementation guide?
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: Thu, 11 Apr 2013 17:22:25 -0000

	Was about datacenters?

	If so, this is the link:

http://datatracker.ietf.org/doc/draft-lopez-v6ops-dc-ipv6/

Regards,
/as

On 4/11/13 1:56 PM, Ackermann, Michael wrote:
> At the most recent IETF Meeting in Orlando, a presentation was given
> regarding a document which contained guidelines for implementing and
> operating IPv6. 
> 
>  
> 
> I agreed to review and comment on this document.
> 
>  
> 
> BUT
> 
>  
> 
> I cannot find it. 
> 
>  
> 
> Can anyone help me locate this document? 
> 
>  
> 
> Thanks,
> 
>  
> 
> Mike
> 
>  
> 
>  
> 
> 
> The information contained in this communication is highly confidential
> and is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you
> are hereby notified that any viewing, copying, disclosure or
> distribution of this information is prohibited. Please notify the
> sender, by electronic mail or telephone, of any unintended receipt and
> delete the original message without making any copies.
> 
> Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and
> Blue Shield Association.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>