[db-wg] "status:" attribute values in the RIPE database

• Previous message (by thread): [db-wg] "status:" attribute values in the RIPE database
• Next message (by thread): [db-wg] NWI-4 - role of status: field in multivalued status context - reprise

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Nick Hilliard nick at foobar.org
Tue Jun 8 13:13:41 CEST 2021

Ronald F. Guilmette via db-wg wrote on 08/06/2021 00:48:
> The last time I checked, there was
> nothing within any of the relevant RFCs that explicity stipulated
> that the user-id portion of an email address either SHALL or MUST or
> SHOULD be treated as case insensitive

the <local> part of an rfc821/rfc2821 email address has always been 
case-sensitive.

Otherwise, almost all if not all tokens in ripe181++ syntax are case 
insensitive, and always needed either case translation or 
case-insensitive comparison to process correctly.

Nick

• Previous message (by thread): [db-wg] "status:" attribute values in the RIPE database
• Next message (by thread): [db-wg] NWI-4 - role of status: field in multivalued status context - reprise

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]