idnits 2.17.1 draft-ietf-lamps-eai-addresses-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5280, updated by this document, for RFC5378 checks: 2005-04-15) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 11, 2018) is 2295 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '0' on line 471 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LAMPS A. Melnikov, Ed. 3 Internet-Draft Isode Ltd 4 Updates: 5280 (if approved) W. Chuang, Ed. 5 Intended status: Standards Track Google, Inc. 6 Expires: July 15, 2018 January 11, 2018 8 Internationalized Email Addresses in X.509 certificates 9 draft-ietf-lamps-eai-addresses-16 11 Abstract 13 This document defines a new name form for inclusion in the otherName 14 field of an X.509 Subject Alternative Name and Issuer Alternative 15 Name extension that allows a certificate subject to be associated 16 with an Internationalized Email Address. 18 This document updates RFC 5280. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on July 15, 2018. 37 Copyright Notice 39 Copyright (c) 2018 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 56 3. Name Definitions . . . . . . . . . . . . . . . . . . . . . . 2 57 4. IDNA2008 . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Matching of Internationalized Email Addresses in X.509 59 certificates . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6. Name constraints in path validation . . . . . . . . . . . . . 5 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 62 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 64 9.1. Normative References . . . . . . . . . . . . . . . . . . 8 65 9.2. Informative References . . . . . . . . . . . . . . . . . 9 66 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 9 67 Appendix B. Example of SmtpUTF8Mailbox . . . . . . . . . . . . . 10 68 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 11 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 71 1. Introduction 73 [RFC5280] defines the rfc822Name subjectAltName name type for 74 representing [RFC5321] email addresses. The syntax of rfc822Name is 75 restricted to a subset of US-ASCII characters and thus can't be used 76 to represent Internationalized Email addresses [RFC6531]. This 77 document defines a new otherName variant to represent 78 Internationalized Email addresses. In addition this document 79 requires all email address domains in X.509 certificates to conform 80 to IDNA2008 [RFC5890]. 82 2. Conventions Used in This Document 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC2119]. 88 The formal syntax uses the Augmented Backus-Naur Form (ABNF) 89 [RFC5234] notation. 91 3. Name Definitions 93 The GeneralName structure is defined in [RFC5280], and supports many 94 different name forms including otherName for extensibility. This 95 section specifies the SmtpUTF8Mailbox name form of otherName, so that 96 Internationalized Email addresses can appear in the subjectAltName of 97 a certificate, the issuerAltName of a certificate, or anywhere else 98 that GeneralName is used. 100 id-on-SmtpUTF8Mailbox OBJECT IDENTIFIER ::= { id-on 9 } 102 SmtpUTF8Mailbox ::= UTF8String (SIZE (1..MAX)) 103 -- SmtpUTF8Mailbox conforms to Mailbox as specified 104 -- in Section 3.3 of RFC 6531. 106 When the subjectAltName (or issuerAltName) extension contains an 107 Internationalized Email address with a non-ASCII local-part, the 108 address MUST be stored in the SmtpUTF8Mailbox name form of otherName. 109 The format of SmtpUTF8Mailbox is defined as the ABNF rule 110 SmtpUTF8Mailbox. SmtpUTF8Mailbox is a modified version of the 111 Internationalized Mailbox which was defined in Section 3.3 of 112 [RFC6531] which was itself derived from SMTP Mailbox from 113 Section 4.1.2 of [RFC5321]. [RFC6531] defines the following ABNF 114 rules for Mailbox whose parts are modified for internationalization: 115 , , , , 116 , and . In particular, was updated to 117 also support UTF8-non-ascii. UTF8-non-ascii was described by 118 Section 3.1 of [RFC6532]. Also, domain was extended to support 119 U-labels, as defined in [RFC5890]. 121 This document further refines Internationalized [RFC6531] Mailbox 122 ABNF rules and calls this SmtpUTF8Mailbox. In SmtpUTF8Mailbox, 123 labels that include non-ASCII characters MUST be stored in U-label 124 (rather than A-label) [RFC5890] form. This restriction removes the 125 need to determine which label encoding A- or U-label is present in 126 the Domain. As per Section 2.3.2.1 of [RFC5890], U-label are encoded 127 as UTF-8 [RFC3629] in Normalization Form C and other properties 128 specified there. In SmtpUTF8Mailbox, domain labels that solely use 129 ASCII characters (meaning not A- nor U-labels) SHALL use NR-LDH 130 restrictions as specified by Section 2.3.1 of [RFC5890] and SHALL be 131 restricted to lower case letters. NR-LDH stands for "Non-Reserved 132 Letters Digits Hyphen" and is the set of LDH labels that do not have 133 "--" characters in the third and forth character position, which 134 excludes "tagged domain names" such as A-labels. Consistent with the 135 treatment of rfc822Name in [RFC5280], SmtpUTF8Mailbox is an envelope 136 and has no phrase (such as a common name) before it, has no 137 comment (text surrounded in parentheses) after it, and is not 138 surrounded by "<" and ">". 140 Due to operational reasons to be described shortly and name 141 constraint compatibility reasons described in Section 6, 142 SmtpUTF8Mailbox subjectAltName MUST only be used when the local-part 143 of the email address contains non-ASCII characters. When the local- 144 part is ASCII, rfc822Name subjectAltName MUST be used instead of 145 SmtpUTF8Mailbox. This is compatible with legacy software that 146 supports only rfc822Name (and not SmtpUTF8Mailbox). The appropriate 147 usage of rfc822Name and SmtpUTF8Mailbox is summarized in Table 1 148 below. 150 SmtpUTF8Mailbox is encoded as UTF8String. The UTF8String encoding 151 MUST NOT contain a Byte-Order- Mark (BOM) [RFC3629] to aid 152 consistency across implementations particularly for comparison. 154 +-----------------+-------------+--------------+-----------------+ 155 | local-part char | domain char | domain label | subjectAltName | 156 +-----------------+-------------+--------------+-----------------+ 157 | ASCII-only | ASCII-only | NR-LDH label | rfc822Name | 158 | non-ASCII | ASCII-only | NR-LDH label | SmtpUTF8Mailbox | 159 | ASCII-only | non-ASCII | A-label | rfc822Name | 160 | non-ASCII | non-ASCII | U-label | SmtpUTF8Mailbox | 161 +-----------------+-------------+--------------+-----------------+ 163 non-ASCII may additionally include ASCII characters. 165 Table 1: Email address formatting 167 4. IDNA2008 169 To facilitate comparison between email addresses, all email address 170 domains in X.509 certificates MUST conform to IDNA2008 [RFC5890] (and 171 avoids any "mappings" mentioned in that document). Use of non- 172 conforming email address domains introduces the possibility of 173 conversion errors between alternate forms. This applies to 174 SmtpUTF8Mailbox and rfc822Name in subjectAltName, issuerAltName and 175 anywhere else that these are used. 177 5. Matching of Internationalized Email Addresses in X.509 certificates 179 In equivalence comparison with SmtpUTF8Mailbox, there may be some 180 setup work on one or both inputs depending of whether the input is 181 already in comparison form. Comparing SmtpUTF8Mailboxs consists of a 182 domain part step and a local-part step. The comparison form for 183 local-parts is always UTF-8. The comparison form for domain parts 184 depends on context. While some contexts such as certificate path 185 validation in [RFC5280] specify transforming domain to A-label 186 (Section 7.5 and 7.2 in [RFC5280] as updated by 187 [ID-lamps-rfc5280-i18n-update]), this document recommends 188 transforming to UTF-8 U-label instead. This reduces the likelihood 189 of errors by reducing conversions as more implementations natively 190 support U-label domains. 192 Comparison of two SmtpUTF8Mailbox is straightforward with no setup 193 work needed. They are considered equivalent if there is an exact 194 octet-for-octet match. Comparison with email addresses such as 195 Internationalized email address or rfc822Name requires additional 196 setup steps for domain part and local-part. The initial preparation 197 for the email addresses is to remove any phrases or comments, as well 198 as "<" and ">" present. This document calls for comparison of domain 199 labels that include non-ASCII characters be transformed to U-label if 200 not already in that form. The first step is to detect use of the 201 A-label by using Section 5.1 of [RFC5891]. Next if necessary, 202 transform any A-labels to U-labels Unicode as specified in 203 Section 5.2 of [RFC5891]. Finally if necessary convert the Unicode 204 to UTF-8 as specified in Section 3 of [RFC3629]. For ASCII NR-LDH 205 labels, upper case letters are converted to lower case letters. In 206 setup for SmtpUTF8Mailbox, the email address local-part MUST conform 207 to the requirements of [RFC6530] and [RFC6531], including being a 208 string in UTF-8 form. In particular, the local-part MUST NOT be 209 transformed in any way, such as by doing case folding or 210 normalization of any kind. The part of an 211 Internationalized email address is already in UTF-8. For rfc822Name 212 the local-part, which is IA5String (ASCII), trivially maps to UTF-8 213 without change. Once setup is complete, they are again compared 214 octet-for-octet. 216 To summarize non-normatively, the comparison steps including setup 217 are: 219 1. If the domain contains A-labels, transform them to U-labels. 221 2. If the domain contains ASCII NR-LDH labels, lowercase them. 223 3. Compare strings octet-for-octet for equivalence. 225 This specification expressly does not define any wildcard characters 226 and SmtpUTF8Mailbox comparison implementations MUST NOT interpret any 227 character as wildcards. Instead, to specify multiple email addresses 228 through SmtpUTF8Mailbox, the certificate MUST use multiple 229 subjectAltNames or issuerAltNames to explicitly carry any additional 230 email addresses. 232 6. Name constraints in path validation 234 This section updates Section 4.2.1.10 of [RFC5280] to extend 235 rfc822Name name constraints to SmtpUTF8Mailbox subjectAltNames. A 236 SmtpUTF8Mailbox aware path validators will apply name constraint 237 comparison to the subject distinguished name and both forms of 238 subject alternative name rfc822Name and SmtpUTF8Mailbox. 240 Both rfc822Name and SmtpUTF8Mailbox subject alternative names 241 represent the same underlying email address namespace. Since legacy 242 CAs constrained to issue certificates for a specific set of domains 243 would lack corresponding UTF-8 constraints, 244 [ID-lamps-rfc5280-i18n-update] updates modifies and extends 245 rfc822Name name constraints defined in [RFC5280] to cover 246 SmtpUTF8Mailbox subject alternative names. This ensures that the 247 introduction of SmtpUTF8Mailbox does not violate existing name 248 constraints. Since it is not valid to include non-ASCII UTF-8 249 characters in the local-part of rfc822Name name constraints, and 250 since name constraints that include a local-part are rarely, if at 251 all, used in practice, name constraints updated in 252 [ID-lamps-rfc5280-i18n-update] admit the forms that represent all 253 addresses at a host or all mailboxes in a domain, and deprecates 254 rfc822Name name constraints that represent a particular mailbox. 255 That is, rfc822Name constraints with a local-part SHOULD NOT be used. 257 Constraint comparison with SmtpUTF8Mailbox subjectAltName starts with 258 the setup steps defined by Section 5. Setup converts the inputs of 259 the comparison which is one of a subject distinguished name or a 260 rfc822Name or SmtpUTF8Mailbox subjectAltName, and one of a rfc822Name 261 name constraint, to constraint comparison form. For rfc822Name name 262 constraint, this will convert any domain A-labels to U-labels. For 263 both the name constraint and the subject, this will lower case any 264 domain NR-LDH labels. Strip the local-part and "@" separator from 265 each rfc822Name and SmtpUTF8Mailbox, leaving just the domain-part. 266 After setup, this follows the comparison steps defined in 4.2.1.10 of 267 [RFC5280] as follows. If the resulting name constraint domain starts 268 with a "." character, then for the name constraint to match, a suffix 269 of the resulting subject alternative name domain MUST match the name 270 constraint (including the leading ".") octet for octet. If the 271 resulting name constraint domain does not start with a "." character, 272 then for the name constraint to match, the entire resulting subject 273 alternative name domain MUST match the name constraint octet for 274 octet. 276 Certificate Authorities that wish to issue CA certificates with email 277 address name constraint MUST use rfc822Name subject alternative names 278 only. These MUST be IDNA2008 conformant names with no mappings, and 279 with non-ASCII domains encoded in A-labels only. 281 The name constraint requirement with SmtpUTF8Mailbox subject 282 alternative name is illustrated in the non-normative diagram 283 Figure 1. The first example (1) illustrates a permitted rfc822Name 284 ASCII only hostname name constraint, and the corresponding valid 285 rfc822Name subjectAltName and SmtpUTF8Mailbox subjectAltName email 286 addresses. The second example (2) illustrates a permitted rfc822Name 287 hostname name constraint with A-label, and the corresponding valid 288 rfc822Name subjectAltName and SmtpUTF8Mailbox subjectAltName email 289 addresses. Note that an email address with ASCII only local-part is 290 encoded as rfc822Name despite also having unicode present in the 291 domain. 293 +-------------------------------------------------------------------+ 294 | Root CA Cert | 295 +-------------------------------------------------------------------+ 296 | 297 v 298 +-------------------------------------------------------------------+ 299 | Intermediate CA Cert | 300 | Permitted | 301 | rfc822Name: elementary.school.example.com (1) | 302 | | 303 | rfc822Name: xn--pss25c.example.com (2) | 304 | | 305 +-------------------------------------------------------------------+ 306 | 307 v 308 +-------------------------------------------------------------------+ 309 | Entity Cert (w/explicitly permitted subjects) | 310 | SubjectAltName Extension | 311 | rfc822Name: student@elemenary.school.example.com (1) | 312 | SmtpUTF8Mailbox: u+5B66u+751F@elementary.school.example.com | 313 | (1) | 314 | | 315 | rfc822Name: student@xn--pss25c.example.com (2) | 316 | SmtpUTF8Mailbox: u+533Bu+751F@u+5927u+5B66.example.com (2) | 317 | | 318 +-------------------------------------------------------------------+ 320 Name constraints with SmtpUTF8Name and rfc822Name 322 Figure 1 324 7. Security Considerations 326 Use of SmtpUTF8Mailbox for certificate subjectAltName (and 327 issuerAltName) will incur many of the same security considerations as 328 in Section 8 in [RFC5280], but introduces a new issue by permitting 329 non-ASCII characters in the email address local-part. This issue, as 330 mentioned in Section 4.4 of [RFC5890] and in Section 4 of [RFC6532], 331 is that use of Unicode introduces the risk of visually similar and 332 identical characters which can be exploited to deceive the recipient. 333 The former document references some means to mitigate against these 334 attacks. 336 8. IANA Considerations 338 In Section 3 and the ASN.1 module identifier defined in Appendix A. 339 IANA is kindly requested to make the following assignments for: 341 The LAMPS-EaiAddresses-2016 ASN.1 module in the "SMI Security for 342 PKIX Module Identifier" registry (1.3.6.1.5.5.7.0). 344 The SmtpUTF8Mailbox otherName in the "PKIX Other Name Forms" 345 registry (1.3.6.1.5.5.7.8). {{ Note to IANA: id-on-smtputf8Name 346 was assigned based on an earlier version of this document. Please 347 change that entry to id-on-SmtpUTF8Mailbox. }} 349 9. References 351 9.1. Normative References 353 [ID-lamps-rfc5280-i18n-update] 354 Housley, R., "Internationalization Updates to RFC 5280", 355 June 2017, . 358 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 359 Requirement Levels", BCP 14, RFC 2119, 360 DOI 10.17487/RFC2119, March 1997, 361 . 363 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 364 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 365 2003, . 367 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 368 Specifications: ABNF", STD 68, RFC 5234, 369 DOI 10.17487/RFC5234, January 2008, 370 . 372 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 373 Housley, R., and W. Polk, "Internet X.509 Public Key 374 Infrastructure Certificate and Certificate Revocation List 375 (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, 376 . 378 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 379 DOI 10.17487/RFC5321, October 2008, 380 . 382 [RFC5890] Klensin, J., "Internationalized Domain Names for 383 Applications (IDNA): Definitions and Document Framework", 384 RFC 5890, DOI 10.17487/RFC5890, August 2010, 385 . 387 [RFC5891] Klensin, J., "Internationalized Domain Names in 388 Applications (IDNA): Protocol", RFC 5891, 389 DOI 10.17487/RFC5891, August 2010, 390 . 392 [RFC6530] Klensin, J. and Y. Ko, "Overview and Framework for 393 Internationalized Email", RFC 6530, DOI 10.17487/RFC6530, 394 February 2012, . 396 [RFC6531] Yao, J. and W. Mao, "SMTP Extension for Internationalized 397 Email", RFC 6531, DOI 10.17487/RFC6531, February 2012, 398 . 400 [RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized 401 Email Headers", RFC 6532, DOI 10.17487/RFC6532, February 402 2012, . 404 9.2. Informative References 406 [RFC5912] Hoffman, P. and J. Schaad, "New ASN.1 Modules for the 407 Public Key Infrastructure Using X.509 (PKIX)", RFC 5912, 408 DOI 10.17487/RFC5912, June 2010, 409 . 411 Appendix A. ASN.1 Module 413 The following ASN.1 module normatively specifies the SmtpUTF8Mailbox 414 structure. This specification uses the ASN.1 definitions from 415 [RFC5912] with the 2002 ASN.1 notation used in that document. 416 [RFC5912] updates normative documents using older ASN.1 notation. 418 LAMPS-EaiAddresses-2016 419 { iso(1) identified-organization(3) dod(6) 420 internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) 421 id-mod-lamps-eai-addresses-2016(TBD) } 423 DEFINITIONS IMPLICIT TAGS ::= 424 BEGIN 426 IMPORTS 427 OTHER-NAME 428 FROM PKIX1Implicit-2009 429 { iso(1) identified-organization(3) dod(6) internet(1) security(5) 430 mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-implicit-02(59) } 432 id-pkix 433 FROM PKIX1Explicit-2009 434 { iso(1) identified-organization(3) dod(6) internet(1) security(5) 435 mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-explicit-02(51) } ; 437 -- 438 -- otherName carries additional name types for subjectAltName, 439 -- issuerAltName, and other uses of GeneralNames. 440 -- 442 id-on OBJECT IDENTIFIER ::= { id-pkix 8 } 444 SmtpUtf8OtherNames OTHER-NAME ::= { on-SmtpUTF8Mailbox, ... } 446 on-SmtpUTF8Mailbox OTHER-NAME ::= { 447 SmtpUTF8Mailbox IDENTIFIED BY id-on-SmtpUTF8Mailbox 448 } 450 id-on-SmtpUTF8Mailbox OBJECT IDENTIFIER ::= { id-on 9 } 452 SmtpUTF8Mailbox ::= UTF8String (SIZE (1..MAX)) 453 -- SmtpUTF8Mailbox conforms to Mailbox as specified 454 -- in Section 3.3 of RFC 6531. 456 END 458 Appendix B. Example of SmtpUTF8Mailbox 460 This non-normative example demonstrates using SmtpUTF8Mailbox as an 461 otherName in GeneralName to encode the email address 462 "u+8001u+5E2B@example.com". 464 The hexadecimal DER encoding of the email address is: 465 A022060A 2B060105 05070012 0809A014 0C12E880 81E5B8AB 40657861 466 6D706C65 2E636F6D 468 The text decoding is: 469 0 34: [0] { 470 2 10: OBJECT IDENTIFIER '1 3 6 1 5 5 7 0 18 8 9' 471 14 20: [0] { 472 16 18: UTF8String '..@example.com' 473 : } 474 : } 476 Figure 2 478 The example was encoded on the OSS Nokalva ASN.1 Playground and the 479 above text decoding is an output of Peter Gutmann's "dumpasn1" 480 program. 482 Appendix C. Acknowledgements 484 Thank you to Magnus Nystrom for motivating this document. Thanks to 485 Russ Housley, Nicolas Lidzborski, Laetitia Baudoin, Ryan Sleevi, Sean 486 Leonard, Sean Turner, John Levine, and Patrik Falstrom for their 487 feedback. Also special thanks to John Klensin for his valuable input 488 on internationalization, Unicode and ABNF formatting, to Jim Schaad 489 for his help with the ASN.1 example and his helpful feedback, and 490 especially to Viktor Dukhovni for helping us with name constraints 491 and his many detailed document reviews. 493 Authors' Addresses 495 Alexey Melnikov (editor) 496 Isode Ltd 497 14 Castle Mews 498 Hampton, Middlesex TW12 2NP 499 UK 501 Email: Alexey.Melnikov@isode.com 503 Weihaw Chuang (editor) 504 Google, Inc. 505 1600 Amphitheater Parkway 506 Mountain View, CA 94043 507 US 509 Email: weihaw@google.com