idnits 2.17.00 (12 Aug 2021) /tmp/idnits51325/draft-rosen-megaco-namepatterns-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. == There are 4 instances of lines with non-ascii characters in the document. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** 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.) ** 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 53: '... MGs SHOULD use one patter...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 12 looks like a reference -- Missing reference section? '00-27' on line 72 looks like a reference -- Missing reference section? '0' on line 74 looks like a reference -- Missing reference section? '3-5' on line 74 looks like a reference -- Missing reference section? '8' on line 74 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Megaco B. Rosen 2 Internet Draft Marconi 3 draft-rosen-megaco-namepatterns-01.txt July, 2002 4 Category: Informational 6 Name Pattern Package for Megaco 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026 [1]. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as Internet- 16 Drafts. Internet-Drafts are draft documents valid for a maximum of 17 six months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- Drafts 19 as reference material or to cite them other than as "work in 20 progress." 21 The list of current Internet-Drafts can be accessed at 22 http://www.ietf.org/ietf/1id-abstracts.txt 23 The list of Internet-Draft Shadow Directories can be accessed at 24 http://www.ietf.org/shadow.html. 26 1. Abstract 28 To construct meaningful audits of terminations while controlling the 29 amount of data sent in response to the audits, it would be very 30 helpful if the MGC understood the way terminations were named in the 31 MG. This package provides a method for obtaining the naming pattern 32 for terminations in an MG. 34 2. Package Description 36 2.1 Naming Pattern Package 38 PackageID: nampat (0x00xx) 39 Version: 1 40 Extends: root 42 Description: This package defines Gateway wide termination naming 43 pattern. 45 2.1.1 Properties 47 Pattern 48 --------------- 49 PropertyId: Pattern (0x0010) 50 Name pattern of a set of terminations in the gateway. 51 Used to discover the names of terminations that 52 can be audited. Includes ephemeral terminations. 53 MGs SHOULD use one pattern for each type of 54 termination (same packages implemented), but no 55 two Patterns can have the same value. 56 Type: String 57 Possible Value: 58 In Text Encoding 59 A string of up to 64 characters using the following 60 characters: 61 a-z,A-Z,0-9, and "/" - the actual character 62 in the name 63 * - any set of characters 64 ?a - any single character 65 ?0 - any digit 66 ?a - any alpha 67 [n,n,..,n] - alternatives, one of the 68 alternatives listed, n can be a substring 69 of alphas or digits 70 [n-n] - range, any number in the range, 71 n can be a number or an alpha, for example 72 [00-27] or [a-e] 73 Note, mixing of alternatives or ranges is allowed, 74 as in: [0,3-5,8] 75 In Binary Encoding 76 An octet string with 77 Bytes 0-3 Variable Mask û ones where the Id 78 pattern varies 79 Bytes 4-7 Fixed Value û the value for the Id 80 where the Variable Mask bit is 0 81 Characteristics: Read-only 82 Defined in: TerminationState 84 MaxPatterns 85 --------------- 86 PropertyId: MaxPatterns (0x0011) 87 The number of patterns in the gateway 88 Type: Integer 89 Possible Value: any integer 90 Characteristics: Read-only 91 Defined in: TerminationState 93 PatternNum 94 --------------- 95 PropertyId: PatternNum (0x0012) 96 Which pattern to read, zero based. Set by the MGC to 97 read a specific pattern in Pattern 98 Type: Integer 99 Possible Value: any integer from zero to MaxPatterns-1 100 Characteristics: Read-Write 101 Defined in: TerminationState 103 2.1.2 Events 105 None 107 2.1.3 Signals 109 None 111 2.1.4 Statistics 113 None 115 2.1.5 Procedures 117 To use this package, one would set PatternNum to the value 0, 118 perhaps using a Modify command), on the Root termination, and then 119 auditValue TerminationState. This would return Pattern(0) and 120 MaxPatterns. One would then change PatternNum to 1, and audit 121 again, repeating until PatternNum = MaxPatterns-1. It is possible 122 to set PatternNum and retrieve the pattern in one command by 123 including the Audit parameter in the Modify command. If PatternNum 124 is set to an illegal value, Error = 455 - Parameter illegal in this 125 Descriptor is returned. In this case PatternNum remains unchanged 126 from previous value. 128 It is recommended, when specifying the names of Terminations, that 129 packages implemented by one pattern are the same, but of course, two 130 patterns could have the same packages implemented on them. Name 131 patterns are simply a way for the MG to tell the MG how to construct 132 efficient wildcards. 134 5. References 136 1 Cuervo, Greene, Huitema, Rayhan, Rosen and Segers ôMegaco 137 Protocol Version 1.0ö, RFC 3015, November, 2000 139 6. Author's Addresses 141 Brian Rosen 142 Marconi 143 1000 Marconi Drive 144 Warrendale, PA 15086 145 USA 146 Phone: +1 (724) 742-6826 147 Email: brian.rosen@marconi.com 148 Full Copyright Statement 150 "Copyright (C) The Internet Society (date). All Rights Reserved. 151 This document and translations of it may be copied and furnished to 152 others, and derivative works that comment on or otherwise explain it 153 or assist in its implmentation may be prepared, copied, published 154 and distributed, in whole or in part, without restriction of any 155 kind, provided that the above copyright notice and this paragraph 156 are included on all such copies and derivative works. However, this 157 document itself may not be modified in any way, such as by removing 158 the copyright notice or references to the Internet Society or other 159 Internet organizations, except as needed for the purpose of 160 developing Internet standards in which case the procedures for 161 copyrights defined in the Internet Standards process must be 162 followed, or as required to translate it into