Re: Getting started on NSIS extensibilty draft

Elwyn Davies <[email protected]>
Newsgroups gmane.ietf.nsis
Message-ID <[email protected]>
Hi, Magnus.

At the last IETF you offered to provide me some guidance on the way
forward with this document.

Since as I understand it, the IESG wants to see this document at the
same time as GIST this is urgent.

The only suggestion I have stemming from comments at the meeting is to
'separate the rules and guidelines.'

Any input gratefully received.
In the meantime I will try to make a 'null' update just to change the
title.

Regards,
Elwyn

Martin Stiemerling wrote:
> The new file name should basically read this way (copy'n'paste error):
> draft-ietf-nsis-ext-00.txt.
>
> Thanks to Hannes for pointing this
>
>  Martin
>
> [email protected]
>
> NEC Laboratories Europe - Network Research Division
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 
>
>   
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of
>> Martin Stiemerling
>> Sent: Monday, January 26, 2009 3:05 PM
>> To: [email protected]
>> Subject: [NSIS] Getting started on NSIS extensibilty draft
>>
>> Dear all,
>>
>> We have a draft to be completed urgently :)
>>
>> Using and Extending the NSIS Protocol Family
>> draft-nsis-ext-02.txt
>>
>> http://tools.ietf.org/html/draft-nsis-ext-02
>>
>>
>> First thing to do is changing the file name to draft-ietf-nsis-ext-
>> 02.txt.
>>
>> Please review it and send your comments.
>>
>>  Martin
>>
>>
>> [email protected]
>>
>> NEC Laboratories Europe - Network Research Division
>> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
>> London W3 6BL | Registered in England 2832014
>>
>> _______________________________________________
>> nsis mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/nsis
>>     
> _______________________________________________
> nsis mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nsis
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.