BLOCKS/BXXP and all this
SASL, TLS usage based other app protocol definitions (eg LDAP)
SASL, TLS defined, invoked via XML-style profiles
Security context is per-connection, not per-channel
Client assertion of service/server name (optional)
ala HTTP 1.1 "Host:" header
helps server choose correct cert to return via TLS
Late-breaking (post -01) changes:
will refer to IANA-registered SASL mechanism names
(shouldn't all IANA registrations be expressible as URIs?)
remove per-mechanism definitions
mechanism params will be blobs, not XML elements
SASL security layer will be supported
rlmorgan
@
washington.edu
[
next
|
top
]
BLOCKS BoF, IETF 47, March 2000