Dear Sandra Murphy, 

I uploaded a new draft in 
http://tools.ietf.org/id/draft-wei-sidr-cta-00.txt.
Could you arrange 10 minutes for me to present it? 

               Title           : A cryptographically generated issuer name 
for trust anchor
                 Author(s)       : Y. Wei, S. Duan, H. Wang
                 Filename        : draft-wei-sidr-cta-00.txt
                 Pages           : 11
                 Date            : 2010-03-01

Abstract

   This document proposes an enhanced certificate profile for trust
   anchors, in which the issuer field of the TA certificate is
   cryptographically generated.  In the RPKI architecture, the trust
   anchor uses self-signed certificate.  However, this sort of
   certificate is vulnerable to various attacks.  For example, the
   attackers can easily create its own public-private key pair and
   declaims that the issuer field belongs to him.  This means attackers
   can easily impersonate the trust anchor.  To address it, this
   document adds identity based cryptographic technique to the self-
   signed certificate.  Since the issuer field of the trust anchor's
   certificate is cryptographically generated from the trust anchor's
   public key, the attacker will not be able to create another key pair
   and declaim that the issuer field generated by the trust anchor
   belongs to him.  Therefore, attackers can not impersonate the trust
   anchor.

Best Regards!

Yinxing Wei
--------------------------------------------------------------------------------
Address: System Architecture Department, Central Institute, ZTE 
Corporation
         Room 2C4, No. 68, Zijinghua Road, Yuhuatai District, Nanjing, 
China
Zipcode: 210012
Office Telephone: +86-025-52877993
Mobile Telephone: +86-13611519358
Fax: +86-25-52878008
MSN: [email protected]
---------------------------------------------------------------------------------



Sandra Murphy <[email protected]> 
发件人:  [email protected]
2010-03-11 21:31

收件人
[email protected]
抄送

主题
[sidr] agenda for IETF 77






In my flurry of messages last week, there was supposed to be one 
containing a request for agenda topics.  That got missed, which probably 
explains why I have received only private requests for agenda topics.

I created an agenda from the list of updated drafts as well as the private 

requests for agenda time.  It is now uploaded.

We have the two back-to-back meeting slots in the morning of Wed, Mar 24. 
I have made no attempt to distinguish the slots in the agenda, but if 
anyone would find it good to have the two slots separated, please reply to 

the list.

If anyone desires to be assigned a slot on the agenda or to be removed 
from the agenda, please let me know.

There is one new topic on the agenda that I was informed of privately, but 

I do not yet have a draft name to mention.

Expect more updates.  Revised agendas are due by 15 Mar, to give people 
time to make their plans, but agenda changes after that are not forbidden 
by the chair.  And there's always the traditional "agenda bashing" first 
topic.

--Sandy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr





--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is 
solely property of the sender's organization. This mail communication is 
confidential. Recipients named above are obligated to maintain secrecy and are 
not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the originator of the 
message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to