RE: draft-stapleton-ttned-01 : Trusted Transactions for Network Enabled Devices

["Jeff Stapleton" <jeff.stapleton@xxxxxxxxxx>]

Excellent question.  The security mechanisms for SNMPv3 are in flux, and
frankly in many environments inadequate.  Further, as network-enabled
devices become more intelligent, SNMPv3 becomes strained to keep up as
application level controls and protocols are deployed.  TTNED is not
designed to replace SNMPv3, rather it is designed to provide a robust
security layer for newer management applications and for existing management
protocols, such as SNMPv3.  The SNMPv3 PDU can be encapsulated within the
TTNED envelop, and the security protections can be added.  

Basically it is an enhancement to new and existing management protocols.
Does that address your question? 
Jeff

-----Original Message-----
From: Timothy J. Miller [mailto:tmiller@xxxxxxxxx] 
Sent: Monday, March 12, 2007 9:34 AM
To: jeff.stapleton@xxxxxxxxxx
Cc: ietf-smime@xxxxxxx
Subject: Re: draft-stapleton-ttned-01 : Trusted Transactions for Network
Enabled Devices

Jeff Stapleton wrote:
> It is my understanding that the internet draft draft-stapleton-ttned-01 
>
<https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=14230>
was 
> assigned to the S/MIME group in January 2007.  This document specifies a 
> cryptographically protected message format and transaction protocol for
managing 
> network-enabled devices. [...]

> My intent is to transition this draft to RFC status.  I would be
interested in 
> generating some dialogue on this document, collecting comments, and
applying 
> changes to make it a better document.  Thanks! 

I'm curious as to what you plan to achieve that's not already covered by 
SNMPv3.

-- Tim