Language Tags in malloc Steve Hanna steve.hanna@sun.com Problem - - PowerPoint PPT Presentation

▶

Oct 30, 2022 172 likes •270 views

Language Tags in malloc Steve Hanna steve.hanna@sun.com Problem Make zone names work in a multilingual environment 239.192.0.0/20 IBM Switzerland 239.192.16.0/20 IBM Geneva Problem: Users speak different languages

SLIDE 1

Language Tags in malloc

Steve Hanna steve.hanna@sun.com

SLIDE 2

Problem

Make zone names work in a multilingual

environment

SLIDE 3

239.192.0.0/20 “IBM Switzerland” 239.192.16.0/20 “IBM Geneva”

SLIDE 4

Problem:

– Users speak different languages

Solution:

– Apply RFC 1766 language tags to zone names – Allow more than one name per zone

This meets requirements of RFC 2277,

which says we must address this.

SLIDE 5

239.192.0.0/20 “en”, “IBM Switzerland” “fr”, “IBM Suisse” 239.192.16.0/20 “en”, “IBM Geneva” “fr”, “IBM Genève”

SLIDE 6

Implications, part 1

MZAP

– Add language tag to zone name – Allow multiple zone names – Add default flag – Conflict in names is detected

MASC & AAP

– No effect

SLIDE 7

Implications, part 2

MDHCP

– Allow host to specify preferred language in MDHCPINFORM – Return best match for each zone – For multilingual hosts, specify no preferred language and return all zone names

SLIDE 8

Implications, part 3

Abstract API

– Scope data type contains all zone names for each zone – get_scope_name returns best match for a specified language tag and Scope

All affected drafts have been updated

SLIDE 9