idnits 2.17.1 draft-ietf-mixer-infotree-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 3 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([2,5], [4], [6,1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 128: '... MAY CONTAIN {mHSNumericCountryName...' RFC 2119 keyword, line 138: '... MUST CONTAIN {aDMDName}...' RFC 2119 keyword, line 148: '... MUST CONTAIN {pRMDName}...' RFC 2119 keyword, line 160: '... MUST CONTAIN {mHSOrganizationName ...' RFC 2119 keyword, line 170: '... MUST CONTAIN {mHSOrganizationalUni...' (7 more instances...) == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document obsoletes RFC1836, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 349 has weird spacing: '...ntifier mHSN...' == Line 350 has weird spacing: '...tribute mHSDo...' -- 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 (August 1997) is 9750 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) -- Missing reference section? '6' on line 459 looks like a reference -- Missing reference section? '1' on line 439 looks like a reference -- Missing reference section? '4' on line 450 looks like a reference -- Missing reference section? '2' on line 442 looks like a reference -- Missing reference section? '5' on line 453 looks like a reference -- Missing reference section? '3' on line 446 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 4 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working S.E. Kille 2 Group Isode Ltd. 3 INTERNET-DRAFT August 1997 4 Obsoletes: RFC 1836 Expires: April 1998 5 File: 6 draft-ietf-mixer-infotree-00.txt 8 Representing the O/R Address hierarchy in the 9 X.500 Directory Information Tree 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, 15 and its Working Groups. Note that other groups may also distribute 16 working documents as Internet Drafts. 17 Internet Drafts are draft documents valid for a maximum of six months. 18 Internet Drafts may be updated, replaced, or obsoleted by other 19 documents at any time. It is not appropriate to use Internet Drafts 20 as reference material or to cite them other than as a ``working 21 draft'' or ``work in progress.'' 22 Please check the I-D abstract listing contained in each Internet Draft 23 directory to learn the current status of this or any other Internet 24 Draft. 26 Abstract 27 This document defines a representation of the O/R Address hierarchy in 28 the Directory Information Tree [6, 1]. This is useful for a range of 29 purposes, including: 31 o Support for MHS Routing [4]. 33 o Support for X.400/RFC 822 address mappings [2, 5]. 35 This draft document will be submitted to the RFC editor as a protocol 36 standard. Distribution of this memo is unlimited. Please send 37 comments to the author or to the discussion group 38 . 40 INTERNET--DRAFT O/R Addresses in the DIT August 1997 42 _Object_Class_______________Mandatory_ 43 mHSCountry M 44 aDMD M 45 pRMD O 46 mHSX121 O 47 mHSNumericUserIdentifier O 48 mHSOrganization O 49 mHSOrganizationalUnit O 50 mHSPerson O 51 mHSNamedObject O 52 mHSTerminalID O 53 mHSDomainDefinedAttribute O 55 Table 1: Order of O/R Address Directory Components 57 1 The O/R Address Hierarchy 59 An O/R Address hierarchy is represented in the X.500 directory by 60 associating directory name components with O/R Address components. An 61 example of this is given in Figure 1. The object classes and 62 attributes required to support this representation are defined in 63 Figure 2. The schema, which defines the hierarchy in which these 64 objects are represented in the directory information tree is specified 65 in Table 1. A given object class defined in the table will always be 66 higher in the DIT than an object class defined lower down the table. 67 Valid combinations of O/R Address components are defined in X.400. 69 INTERNET--DRAFT O/R Addresses in the DIT August 1997 71 @ @ 73 C=GB @ @ Numeric-C=234 74 @ @ 76 ___________________________@R_oeS............. 77 | Country | _____S 79 |__aeaeHH___ | 80 aaee H H H ADMD=Gold 400 81 ADMD=" "aaee H H H 82 ________aeae=_ ______H_HHj_ 84 |ADMD | | ADMD | 86 |____Q_Q_Q__| |_____@@____ | 88 Q QQPRMD=UK.AC @ @ PRMD=UK.AC 89 __Q_QQs_____ @ @ 91 | PRMD ________________@@R_oe_SS.............| 93 |___________ | 95 O=UCL 96 ____________ 98 | MHS-Org | 100 |______Q_Q__ | 101 Q Q 102 Q QOU=CS 103 QQ 104 _____QQs____ 106 | MHS-OU | 107 |___________ | 109 Figure 1: Example O/R Address Tree 111 INTERNET--DRAFT O/R Addresses in the DIT August 1997 113 _______________________________________________________________________ 114 IMPORTS 115 ub-domain-name-length, ub-organization-name-length, 116 ub-organizational-unit-name-length, ub-common-name-length, 117 ub-x121-address-length, ub-domain-defined-attribute-type-length, 118 ub-domain-defined-attribute-value-length, ub-terminal-id-length, 119 ub-numeric-user-id-length, ub-country-name-numeric-length, 120 ub-surname-length, ub-given-name-length, ub-initials-length, 121 ub-generation-qualifier-length 123 FROM MTSUpperBounds {joint-iso-ccitt mhs-motis(6) mts(3) 10 124 modules(0) upper-bounds(3) }; 126 mHSCountry OBJECT-CLASS ::= { 127 SUBCLASS OF {country} 128 MAY CONTAIN {mHSNumericCountryName} 129 ID oc-mhs-country} 131 mHSNumericCountryName ATTRIBUTE ::= { 132 WITH SYNTAX NumericString (SIZE (1..ub-country-name-numeric-length)) 133 SINGLE VALUE 20 134 ID at-mhs-numeric-country-name} 136 aDMD OBJECT-CLASS ::= { 137 SUBCLASS OF {top} 138 MUST CONTAIN {aDMDName} 139 ID oc-admd} 141 aDMDName ATTRIBUTE ::= { 142 SUBTYPE OF name 143 WITH SYNTAX DirectoryString {ub-domain-name-length} 30 144 ID at-admd-name} 146 pRMD OBJECT-CLASS ::= { 147 SUBCLASS OF {top} 148 MUST CONTAIN {pRMDName} 149 ID oc-prmd} 151 pRMDName ATTRIBUTE ::= { 152 SUBTYPE OF name 153 WITH SYNTAX DirectoryString {ub-domain-name-length} 40 154 ID at-prmd-name} 156 INTERNET--DRAFT O/R Addresses in the DIT August 1997 158 mHSOrganization OBJECT-CLASS ::= { 159 SUBCLASS OF {top} 160 MUST CONTAIN {mHSOrganizationName } 161 ID oc-mhs-organization} 163 mHSOrganizationName ATTRIBUTE ::= { 164 SUBTYPE OF organizationName 165 WITH SYNTAX DirectoryString {ub-organization-name-length} 50 166 ID at-mhs-organization-name} 168 mHSOrganizationalUnit OBJECT-CLASS ::= { 169 SUBCLASS OF {top} 170 MUST CONTAIN {mHSOrganizationalUnitName} 171 ID oc-mhs-organizational-unit} 173 mHSOrganizationalUnitName ATTRIBUTE ::= { 174 SUBTYPE OF organizationalUnitName 60 175 WITH SYNTAX DirectoryString {ub-organizational-unit-name-length} 176 ID at-mhs-organizational-unit-name} 178 mHSPerson OBJECT-CLASS ::= { 179 SUBCLASS OF {top} 180 MUST CONTAIN {mHSSurname} 181 MAY CONTAIN {mHSGivenName| 182 mHSInitials| 183 mHSGenerationalQualifier} 184 ID oc-mhs-person} 70 186 mHSSurname ATTRIBUTE ::= { 187 SUBTYPE OF surname 188 WITH SYNTAX DirectoryString {ub-surname-lenght} 189 ID at-mhs-surname} 191 mHSGivenName ATTRIBUTE ::= { 192 SUBTYPE OF givenName 193 WITH SYNTAX DirectoryString {ub-given-name-length} 194 ID at-mhs-given-name} 80 196 mHSInitials ATTRIBUTE ::= { 197 SUBTYPE OF initials 198 WITH SYNTAX DirectoryString {ub-initials-length} 199 ID at-mhs-initials} 201 INTERNET--DRAFT O/R Addresses in the DIT August 1997 203 mHSGenerationQualifier ATTRIBUTE ::= { 204 SUBTYPE OF generationQualifier 205 WITH SYNTAX DirectoryString {ub-generation-qualifier-length} 206 ID at-mhs-generation-qualifier} 90 208 mHSNamedObject OBJECT-CLASS ::= { 209 SUBCLASS OF {top} 210 MUST CONTAIN {mHSCommonName} 211 ID oc-mhs-named-object} 213 mHSCommonName ATTRIBUTE ::= { 214 SUBTYPE OF commonName 215 WITH SYNTAX DirectoryString {ub-common-name-length} 216 ID at-mhs-common-name} 100 218 mHSX121 OBJECT-CLASS ::= { 219 SUBCLASS OF {top} 220 MUST CONTAIN {mHSX121Address} 221 ID oc-mhs-x121} 223 mHSX121Address ATTRIBUTE ::= { 224 SUBTYPE OF name 225 WITH SYNTAX DirectoryString {ub-x121-address-length} 226 ID at-x121-address} 110 228 mHSDomainDefinedAttribute OBJECT-CLASS ::= { 229 SUBCLASS OF {top} 230 MUST CONTAIN { 231 mHSDomainDefinedAttributeType| 232 mHSDomainDefinedAttributeValue} 233 ID oc-mhs-domain-defined-attribute} 235 mHSDomainDefinedAttributeType ATTRIBUTE ::= { 236 SUBTYPE OF name 120 237 WITH SYNTAX DirectoryString {ub-domain-defined-attribute-type-length} 238 SINGLE VALUE 239 ID at-mhs-domain-defined-attribute-type} 241 mHSDomainDefinedAttributeValue ATTRIBUTE ::= { 242 SUBTYPE OF name 243 WITH SYNTAX DirectoryString {ub-domain-defined-attribute-value-length} 244 SINGLE VALUE 245 ID at-mhs-domain-defined-attribute-value} 246 130 248 INTERNET--DRAFT O/R Addresses in the DIT August 1997 250 mHSTerminalID OBJECT-CLASS ::= { 251 SUBCLASS OF {top} 252 MUST CONTAIN {mHSTerminalIDName} 253 ID oc-mhs-terminal-id} 255 mHSTerminalIDName ATTRIBUTE ::= { 256 SUBTYPE OF name 257 WITH SYNTAX DirectoryString {ub-terminal-id-length} 258 ID at-mhs-terminal-id-name} 140 260 mHSNumericUserIdentifier OBJECT-CLASS ::= { 261 SUBCLASS OF {top} 262 MUST CONTAIN {mHSNumericUserIdentifierName} 263 ID oc-mhs-numeric-user-id} 265 mHSNumericeUserIdentifierName ATTRIBUTE ::= { 266 SUBTYPE OF name 267 WITH SYNTAX DirectoryString {ub-numeric-user-id-length} 150 268 ID at-mhs-numeric-user-id-name} 270 ___________________Figure_2:__O/R_Address_Hierarchy____________________ 272 The hierarchy is defined so that: 274 1. The representation is defined so that it is straightforward to 275 make a mechanical transformation in either direction. This 276 requires that each node is named by an attribute whose type can 277 determine the mapping. 279 2. Where there are multiple domain defined attributes, the first in 280 the sequence is the most significant. 282 3. Physical Delivery (postal) addresses are not represented in this 283 hierarchy. This is primarily because physical delivery can be 284 handled by the Access Unit routing mechanisms defined in [4], and 285 there is no need for this representation. 287 4. Terminal and network forms of address are not handled, except for 288 X.121 form, which is useful for addressing faxes. 290 5. MHSCountry is defined as a subclass of Country, and so the same 291 INTERNET--DRAFT O/R Addresses in the DIT August 1997 293 entry will be used for MHS Routing as for the rest of the DIT. 295 6. The numeric country code will be an alias. 297 7. ADMD will always be present in the hierarchy. This is true in the 298 case of `` '' and of ``0''. This facilitates an easy mechanical 299 transformation between the two forms of address. 301 8. Each node is named by the relevant part of the O/R Address. 303 9. Aliases may be used in other parts of the tree, in order to 304 normalise alternate values. Where an alias is used, the value of 305 the alias should be present as an alternate value in the node 306 aliased to. Aliases may not be used for domain defined 307 attributes. 309 10. Domain Defined Attributes are named by a multi-valued RDN 310 (Relative Distinguished Name), consisting of the type and value. 311 This is done so that standard attribute syntaxes can be used. 313 11. Where an O/R Address has a valid Printable String and T.61 form, 314 both must be present, with one as an alias for the other. This is 315 so that direct lookup of the name will work, independent of the 316 variant used. When both are present in an O/R Address being 317 looked up, either may be used to construct the distinguished name. 319 12. Personal name is handled by use of the mHSPerson object class. 320 Each of the components of the personal name will be present in the 321 relative distinguished name, which will usually be multi-valued. 323 The relationship between X.400 O/R Addresses and the X.400 Entries 324 (Attribute Type and Object Class) are given in Table 2. Where there 325 are multiple Organizational Units or Domain Defined Attributes, each 326 component is mapped onto a single X.500 entry. 328 Note: When an X.121 address is used for addressing fax transmission, 329 this may only be done relative to the PRMD or ADMD. This is in 330 line with the current X.400 standards position. This means that 331 it is not possible to use this form of addressing for an 332 organisational or departmental fax gateway service. 334 INTERNET--DRAFT O/R Addresses in the DIT August 1997 336 O/R_Address__Object_Class_______________Naming_Attribute________________ 337 C mHSCountry countryName 338 or 339 mHSNumericCountryName 340 A aDMD aDMDName 341 P pRMD pRMDName 342 O mHSOrganization mHSOrganizationName 343 OU/OU1/OU2 mHSOrganizationalUnit mHSOrganizationalUnitName 344 OU3/OU4 345 PN mHSPerson personName 346 CN mHSNamedObject mHSCommonName 347 X121 mHSX121 mHSX121Address 348 T-ID mHSTerminalID mHSTerminalIDName 349 UA-ID mHSNumericUserIdentifier mHSNumericUserIdentifierName 350 DDA mHSDomainDefinedAttribute mHSDomainDefinedAttributeType 351 and 352 mHSDomainDefinedAttributeValue 354 Table 2: O/R Address relationship to Directory Name 356 2 Notation 358 O/R Addresses are written in the standard X.400 Notation. 359 Distinguished Names use the string representation of distinguished 360 names defined in [3]. The keywords used for the attributes defined in 361 this specification are given in Table 3. 363 3 Example Representation 365 The O/R Address: 367 I=S; S=Kille; OU1=CS; O=UCL, 368 P=UK.AC; A=Gold 400; C=GB; 370 would be represented in the directory as: 372 MHS-I=S + MHS-S=Kille, MHS-OU=CS, MHS-O=UCL, 373 INTERNET--DRAFT O/R Addresses in the DIT August 1997 375 _Attribute_______________________Keyword_____________ 376 mHSNumericCountryName MHS-Numeric-Country 377 aDMDName ADMD 378 pRMDName PRMD 379 mHSOrganizationName MHS-O 380 mHSOrganizationalUnitName MHS-OU 381 mHSSurname MHS-S 382 mHSGivenName MHS-G 383 mHSInitials MHS-I 384 mHSGenerationalQualifier MHS-GQ 385 mHSCommonName MHS-CN 386 mHSX121Address MHS-X121 387 mHSDomainDefinedAttributeType MHS-DDA-Type 388 mHSDomainDefinedAttributeValue MHS-DDA-Value 389 mHSTerminalIDName MHS-T-ID 390 mHSNumericeUserIdentifierName MHS-UA-ID 392 Table 3: Keywords for String DN Representation 394 PRMD=UK.AC, ADMD=Gold 400, C=GB 396 4 Mapping from O/R Address to Directory Name 398 The primary application of this mapping is to take an X.400 encoded 399 O/R Address and to generate an equivalent directory name. This 400 mapping is only used for selected types of O/R Address: 402 o Mnemonic form 404 o Numeric form 406 o Terminal form, where country is present and X121 addressing is 407 used 409 Other forms of O/R address are handled by Access Unit mechanisms. 410 The O/R Address is treated as an ordered list, with the order as 411 defined in Table 1. For each O/R Address attribute, generate the 412 equivalent directory naming attribute. In most cases, the mapping is 413 INTERNET--DRAFT O/R Addresses in the DIT August 1997 415 mechanical. Printable String or Teletex encodings are chosen as 416 appropriate. Where both forms are present in the O/R Address, either 417 form may be used to generate the distinguished name. Both will be 418 represented in the DIT. There are two special cases: 420 1. A DDA generates a multi-valued RDN 422 2. The Personal Name is mapped to a multi-valued RDN 424 In many cases, an O/R Address will be provided, and only the higher 425 components of the address will be represented in the DIT. In this 426 case, the ``longest possible match'' should be returned. 428 5 Mapping from Directory Name to O/R Address 430 The reverse mapping is also needed in some cases. All of the naming 431 attributes are unique, so the mapping is mechanically reversible. 433 6 Acknowledgements 435 Acknowledgements for work on this document are given in [4]. 437 References 439 [1] The Directory --- overview of concepts, models and services, 440 1993. CCITT X.500 Series Recommendations. 442 [2] S.E. Kille. Mapping between X.400(1988) / ISO 10021 and RFC 822. 443 Request for Comments 1327, Department of Computer Science, 444 University College London, May 1992. 446 [3] S.E. Kille. A string representation of distinguished name. 447 Request for Comments 1485, Department of Computer Science, 448 University College London, January 1992. 450 [4] S.E. Kille. Use of the X.500 directory to support mapping between 451 X.400 and RFC 822 addresses, September 1994. Internet Draft. 453 [5] S.E. Kille. X.400-MHS use of the X.500 directory to support 454 INTERNET--DRAFT O/R Addresses in the DIT August 1997 456 X.400-MHS routing. Request for Comments RFC 1801, Isode Ltd., 457 June 1995. 459 [6] CCITT recommendations X.400 / ISO 10021, April 1988. CCITT 460 SG 5/VII / ISO/IEC JTC1, Message Handling: System and Service 461 Overview. 463 7 Security Considerations 465 Security considerations are not discussed in this INTERNET--DRAFT. 467 8 Author's Address 469 Steve Kille 470 Isode Ltd. 471 The Dome 472 The Square 473 Richmond 474 TW9 1DT 475 England 477 Phone: +44-181-332-9091 479 Internet EMail: S.Kille@ISODE.COM 481 X.400: I=S; S=Kille; P=ISODE; A=Mailnet; C=FI; 483 INTERNET--DRAFT O/R Addresses in the DIT August 1997 485 A Object Identifier Assignment 486 INTERNET--DRAFT O/R Addresses in the DIT August 1997 488 _______________________________________________________________________ 489 mhs-ds OBJECT IDENTIFIER ::= {iso(1) org(3) dod(6) internet(1) private(4) 490 enterprises(1) isode-consortium (453) mhs-ds (7)} 492 tree OBJECT IDENTIFIER ::= {mhs-ds 2} 494 oc OBJECT IDENTIFIER ::= {tree 1} 495 at OBJECT IDENTIFIER ::= {tree 2} 497 oc-admd OBJECT IDENTIFIER ::= {oc 1} 10 498 oc-mhs-country OBJECT IDENTIFIER ::= {oc 2} 499 oc-mhs-domain-defined-attribute OBJECT IDENTIFIER ::= {oc 3} 500 oc-mhs-named-object OBJECT IDENTIFIER ::= {oc 4} 501 oc-mhs-organization OBJECT IDENTIFIER ::= {oc 5} 502 oc-mhs-organizational-unit OBJECT IDENTIFIER ::= {oc 6} 503 oc-mhs-person OBJECT IDENTIFIER ::= {oc 7} 504 oc-mhs-x121 OBJECT IDENTIFIER ::= {oc 8} 505 oc-prmd OBJECT IDENTIFIER ::= {oc 9} 506 oc-mhs-terminal-id OBJECT IDENTIFIER ::= {oc 10} 507 oc-mhs-numeric-user-id OBJECT IDENTIFIER ::= {oc 11} 20 509 at-admd-name OBJECT IDENTIFIER ::= {at 1} 510 at-mhs-common-name OBJECT IDENTIFIER ::= {at 2} 511 at-mhs-domain-defined-attribute-type OBJECT IDENTIFIER ::= {at 3} 512 at-mhs-domain-defined-attribute-value OBJECT IDENTIFIER ::= {at 4} 513 at-mhs-numeric-country-name OBJECT IDENTIFIER ::= {at 5} 514 at-mhs-organization-name OBJECT IDENTIFIER ::= {at 6} 515 at-mhs-organizational-unit-name OBJECT IDENTIFIER ::= {at 7} 516 at-prmd-name OBJECT IDENTIFIER ::= {at 10} 517 at-x121-address OBJECT IDENTIFIER ::= {at 12} 30 518 at-mhs-terminal-id-name OBJECT IDENTIFIER ::= {at 13} 519 at-mhs-numeric-user-id-name OBJECT IDENTIFIER ::= {at 14} 520 at-mhs-surname OBJECT IDENTIFIER ::= {at 15} 521 at-mhs-given-name OBJECT IDENTIFIER ::= {at 16} 522 at-mhs-initials OBJECT IDENTIFIER ::= {at 17} 523 at-mhs-generation-qualifier OBJECT IDENTIFIER ::= {at 18} 525 _______________Figure_3:__Object_Identifier_Assignment_________________