Re: [storm] iSCSI and Unicode (newprep BOF)

["Paul Koning" <[e-mail]>]

Re "Any update SHOULD be backward compatible with RFC 3722" -- I don't understand the "SHOULD".  The obvious word is "MUST".  More precisely -- and maybe this is where the "SHOULD" came in? -- an IQN that was legal under RFC 3722 must still be legal, and two names that under the old rules were considered different must still be different. 

Do you have a pointer to places to start to learn what newprep is all about?

	paul 

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf
> Of [e-mail]
> Sent: Monday, March 22, 2010 10:23 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: [storm] iSCSI and Unicode (newprep BOF)
> 
> I'll be giving a short presentation on iSCSI and Unicode to the newprep
> BOF tomorrow afternoon in Anaheim:
> http://www.ietf.org/proceedings/10mar/slides/newprep-2.pdf
> 
> The short story here is that Unicode and international domain names
> have moved beyond the stringprep technique that iSCSI uses (RFC 3722 is
> the stringprep profile for iSCSI), so this BOF is exploring a framework
> update to stringprep that should allow iSCSI to move forward with
> Unicode changes.
> 
> For anyone interested in exploring further, the rest of the materials
> for this BOF would be a good place to start.
> 
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> [phone]             FAX: [phone]
> [e-mail]        Mobile: [phone]
> ----------------------------------------------------
> 
> _______________________________________________
> storm mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/storm