[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [netext] Consensus call to adopt I-D: draft-korhonen-netext-redirect as WG doc



Hi,

I also support the adoption of the draft as WG document.

Carlos

On Tue, 2009-10-13 at 14:04 +0800, Jinwei Xia wrote:
> Hi,
>  
> I support to adopt it to WG doc. It is appropriate time to go forward.
> Thank you~!
>  
>  
> BR
> Jinwei
> 
> 
>         
>         ______________________________________________________________
>         From: netext-bounces at ietf.org [mailto:netext-bounces at ietf.org]
>         On Behalf Of Basavaraj.Patil at nokia.com
>         Sent: Thursday, October 08, 2009 8:36 PM
>         To: netext at ietf.org
>         Subject: [netext] Consensus call to adopt I-D:
>         draft-korhonen-netext-redirect as WG doc
>         
>         
>         
>          
>         Hello,
>          
>         One of the Netext WG milestones is:
>         Sep 2009                  Initial WG draft on LMA Redirection
>          
>         At IETF75, I-D draft-korhonen-netext-redirect was accepted as
>         the
>         baseline to be adopted as the doc. Process requires that we
>         also run
>         the consensus call on the WG ML.
>          
>         The I-D: Runtime LMA Assignment Support for Proxy Mobile IPv6,
>         draft-korhonen-netext-redirect-04.txt has now been posted and
>         this is
>         a consensus call for its adoption as WG doc.
>         http://www.ietf.org/id/draft-korhonen-netext-redirect-04.txt
>          
>         Please respond by Oct 15th, 09. 
>          
>         -Chairs
>          
> _______________________________________________
> netext mailing list
> netext at ietf.org
> https://www.ietf.org/mailman/listinfo/netext
-- 
Carlos Jesús Bernardos Cano     http://www.netcoms.net
GPG FP: D29B 0A6A 639A A561 93CA  4D55 35DC BA4D D170 4F67

Attachment: signature.asc
Description: This is a digitally signed message part


Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.