Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?

[Brian Weis <[e-mail]>]

Hi Lars,

On Jan 28, 2008, at 2:26 AM, Lars Eggert wrote:

> Hi,
>
> On 2008-1-28, at 11:59, ext Francois Le Faucheur IMAP wrote:
>> On 24 Jan 2008, at 18:04, Lars Eggert wrote:
>>
>>> (individual hat on)
>>>
>>> I'm not convinced that this document needs to be a TSVWG  
>>> document. It's an Informational document that surveys group  
>>> keying options for RSVP, and as such could be published directly  
>>> through the RFC Editor.
>>
>> I am not aware of any solution currently available from the IETF  
>> to actually deploy such distribution of group keys for RSVP.
>> This could, for example, be easily achieved with small extensions  
>> to GDOI (draft-weis-gdoi-for-rsvp), but a solution will only be  
>> defined in IETF (e.g. by MSEC) if the corresponding need is  
>> established by the TSVWG.
>
> based on the discussions in Vancouver, I thought the goal of this  
> document was to survey the options for group keying for RSVP. I  
> don't see how such a survey would motivate the need for any sort of  
> solution work. Meaning that even if this survey finds that none of  
> the existing options are always satisfactory, that's a finding that  
> to me still doesn't immediately motivate the need to develop any  
> new solution. New protocol work should be motivated by an  
> application requiring it.

Calling draft-behringer-tsvwg a "survey" of "group keying for RSVP"  
isn't an entirely accurate statement. It's a much more fundamental  
description of RSVP security: it documents the RSVP trust model  
(perhaps for the first time), and from there it describes the  
appropriate uses for RSVP keys that should be used within different  
network topologies, as well as provisioning methods for those keys.  
Although these topics don't motivate new TSVWG protocol development,  
taking ownership of these RSVP security fundamentals is important for  
TSVWG. I believe that is a good rationale for accepting draft- 
behringer-tsvwg as a WG item.

Thanks,
Brian

-- 
Brian Weis
Advanced Security Development, Security Technology Group, Cisco Systems
Telephone: [phone]
Email: [e-mail]