Re: Call for consensus draft-loughney-nsis-ext-02.txt as WG document?

Xiaoming Fu <[email protected]>
Newsgroups gmane.ietf.nsis
Message-ID <[email protected]>
I agree it is really good to have this document to become WG doc.
Xiaoming


Martin Stiemerling wrote:
> Hi Hannes,
> 
> 
> Am 01.10.2007 um 11:52 schrieb Hannes Tschofenig:
> 
>> Hi Martin
>>
>> I agree that such a document is useful.
>>
>> There are, however, a few follow-up questions:
>> a) When do you write such a document?
>> b) What is the scope of the document?
>>
>> Regarding (a): In the RADEXT and the DIME working group we are 
>> currently producing documents that provide sort of design guidelines, see
>> http://www.ietf.org/internet-drafts/draft-ietf-dime-app-design-guide-02.txt
>> http://www.ietf.org/internet-drafts/draft-ietf-radext-design-00.txt
>>
>> These two documents are written based on the experience that something 
>> went wrong regarding the way how people extended the protocol. Maybe 
>> it would have been better to write these documents earlier. Now we 
>> obviously have much more bad examples to write about.
> 
> We are in the lucky situation to write such a document before things can 
> go wrong. That is a good reasons to start now.
> 
>>
>> Regarding (b): Should the document focus only on GIST or should it 
>> also cover the NSLPs? What happens if you define a new NSLP - do you 
>> revise the document?
> 
> It should cover the whole NSIS stack, i.e., GIST and the NSLPs. When you 
> are tying to extend NSIS as such, you first need to find out the right 
> place to do the extension. 
> 
>>
>> How far can this document go beyond the already described information 
>> found in GIST, and the NSLPs? I could, for example, imagine that 
>> someone gives details about the common design aspects where you could 
>> essentially "steal" text from existing NSLPs.
> 
> This is a good point. 
> 
>   Martin
> 
>>
>> Ciao
>> Hannes
>>
>>
>>
>> Martin Stiemerling wrote:
>>> Hi all,
>>>
>>> Some time ago, John wrote the draft draft-loughney-nsis-ext-02.txt 
>>> discussing the extensibility of NSIS.
>>>
>>> It has been discussed on the mailing list, plus during the IETF 
>>> meetings and it seems to be a good shape to become a WG document.
>>>
>>> Therefore, I would like to propose draft-loughney-nsis-ext-02.txt 
>>> becoming a WG draft by now.
>>>
>>> This requires consensus of WG to do so.
>>>
>>> Please send your opinion on whether you like to see 
>>> draft-loughney-nsis-ext-02.txt as WG document or not to the NSIS 
>>> mailing list by no later than Oct 4th 5pm PST.
>>>
>>> Thanks,
>>>
>>>   Martin
>>>
>>> [email protected] <mailto:[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] <mailto:[email protected]>
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>
>>>   
>>>
>>
> 
> [email protected] <mailto:[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://www1.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.