RE: : End-to-End Security in RFC 3588

Hi Timothy,
 
Due to lack of interest and concrete plans to implement CMS, the work
was abandoned.  
 
John 


________________________________

	From: [email protected] [mailto:[email protected]] On
Behalf Of ext Timothy Smith
	Sent: 18 October, 2005 00:23
	To: [email protected]
	Subject: [AAA-WG]: End-to-End Security in RFC 3588
	
	

	Hi All, 
	
	In Section 2.9, End-to-End Security Framework,  RFC 3588
mentions: 
	
	   End-to-end security services include confidentiality and
message
	  origin authentication.  These services are provided by
supporting AVP
	  integrity and confidentiality between two peers, communicating
	  through agents.
	
	  End-to-end security is provided via the End-to-End security
	  extension, described in [AAACMS].  The circumstances requiring
the
	  use of end-to-end security are determined by policy on each of
the
	  peers. Security policies, which are not the subject of
	  standardization, may be applied by next hop Diameter peer or
by
	  destination realm.  For example, where TLS or IPsec
transmission-
	  level security is sufficient, there may be no need for
end-to-end
	  security. 
	
	I could not find [AAACMS] either as an Internet-Draft or an RFC.
Has this work been completed?  And does anyone have the RFC number?  Or,
has this work been abandoned? 
	
	Thanks for any help. 
	
	Best Regards, 
	Timothy Smith 
	
	[email protected]
	(919) 254-4723