Re: [rt.icann.org #3528] FW: General Request for Assignments (ppp-numbers)

Vernon Schryver <[email protected]>
Newsgroups gmane.ietf.pppext
Message-ID <[email protected]>
> From: James Carlson <[email protected]>

> Unfortunately, Vern's RFC 3818 doesn't cover ECP assignments, so it
> appears we're still stuck with expert review.  That means we need to
> discuss it here and report consensus back.

My now vague recollections are that 3818 does not mention ECP because
a similar document was advanced specifically for ECP.  I can't seem
to find it in the RFC index.

> I read through BB84, and it appears to be a key-exchange protocol, not
> an encryption algorithm.  Also, it appears to work only with direct
> access to physical media and not with the regular bit stream that PPP
> itself requires.  Thus, I suspect it may not be really appropriate as
> an ECP option, though I suppose it may open up a possibly interesting
> discussion about whether we *should* talk about key distribution as an
> ECP option.  (Whether of the ordinary algorithmic sort, or the more
> hand-wavy x-files area-51 "quantum" sort.)

Where did you read about BB84 for PPP?  

My first thought when I read the message from Michelle Cotton was that
someone is playing a practical joke on the IANA.  It is possible that
someone sane seriously wants to do PPP with quantum cryptography, but
I'd like to see an I-D or at least something more substantial than the
short note from Mohamed Ali.

There have been some serious quantum cryptography efforts that I'd not
call hand-wavy x-files area-51, but they've all been a little "academic"
as opposed to "industrial."  Before the IANA fires up a registry, there
must be an IETF protocol that would use it.  So where is the I-D?


Vernon Schryver    [email protected]

_______________________________________________
Pppext mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pppext
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.