Re: I intend to have a document ready for Atlanta on this subject.

A
> > There may be one key derived from mailto:[email protected] and another
> > from sip:[email protected] . The opportunistic PKI infrastructure must be
> > flexible enough to accommodate both and NAPTR records do that by allowing
> > the ABNF syntax for the NAPTR service field to be defined by and listing
> > the application protocol the application supports.
> > as an example..
>
>Ugh, NAPTR.
>
>an Email signature key for [email protected] would be a different
>keytype from SIP, they would be used in different contexts.  SIP is
>a pretty good candidate for using IPsec,

yes but some folks are also interested in encrypting the RTP stream as well.

>for example, whereas email
>isn't because it does through so many intermediate systems.  Email
>key types already exist (PGP, SMIME), so shoehorning them into
>the same RDATA format with HTTPS keys seems no good.
>
>--
>David Terrell           | "We must go forward, not backwards; upwards,
>Nebcorp Prime Minister  | not forwards; and always twirling, twirling,
>[email protected]            | twirling towards freedom!"
>http://wwn.nebcorp.com/ |  - The Simpsons


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto:[email protected]> or <mailto:[email protected]>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<