< draft-ietf-megaco-errata-02.txt   draft-ietf-megaco-errata-03.txt >
Media Gateway Control P.T. Taylor Media Gateway Control P.T. Taylor
Internet Draft Nortel Networks Internet Draft Nortel Networks
Document: draft-ietf-megaco-errata-02.txt May 2000 Document: draft-ietf-megaco-errata-03.txt May 2000
Category: Standards Track Category: Standards Track
Megaco Errata Megaco Errata
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 39 skipping to change at line 40
protocol document [2], along with the changes proposed in the text protocol document [2], along with the changes proposed in the text
of that document to resolve them. After joint IETF/ITU-T Study Group of that document to resolve them. After joint IETF/ITU-T Study Group
16 approval of these corrections, they will be incorporated into the 16 approval of these corrections, they will be incorporated into the
final decided version of H.248 and the corresponding Megaco protocol final decided version of H.248 and the corresponding Megaco protocol
RFC. The current status of approval is as follows: RFC. The current status of approval is as follows:
. IETF process is complete, and the IESG has granted its approval; . IETF process is complete, and the IESG has granted its approval;
. ITU-T process is complete except that the Members' comment period . ITU-T process is complete except that the Members' comment period
does not expire until June 8, 2000 and the final act of Decision does not expire until June 8, 2000 and the final act of Decision
is scheduled for June 15, 2000. is scheduled for June 15, 2000.
This draft has been modified from the previous issue by additional This draft has been modified from the previous issue by
comments received from the ITU-T and the IESG. All changes are strengthening the sentence in section D.1.3 which requires
listed in the body of this document. The significant change is as exponential backoff in the face of congestion. The detailed list of
follows: changes from draft-ietf-megaco-errata-01.txt has been left intact
. section D.1.3: exponential backoff in the face of congestion is for the user's convenience.
made mandatory.
Taylor Standards Track -- Expires Nov 2000 1
2. Conventions used in this document 2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119 [1]. this document are to be interpreted as described in RFC-2119 [1].
Taylor Standards Track -- Expires Nov 2000 1
3. Errata 3. Errata
All section numbers are those of the relevant text of [2]. All section numbers are those of the relevant text of [2].
3.1 Changes From Previous Issue 3.1 Changes From draft-ietf-megaco-errata-01.txt
Section 7.1: proposed change in the comment preceding production Section 7.1: proposed change in the comment preceding production
auditReturnItem in Annex B.2 (ABNF) has been deleted, because a auditReturnItem in Annex B.2 (ABNF) has been deleted, because a
later section actually proposes deletion of the comment. later section actually proposes deletion of the comment.
Section 7.2.5: issue has been expanded to note that the text of Section 7.2.5: issue has been expanded to note that the text of
section 7.2.5 anticipates the possibility of return of multiple section 7.2.5 anticipates the possibility of return of multiple
instances of the same descriptor. Proposed remedy is to delete the instances of the same descriptor. Proposed remedy is to delete the
restrictive comment in front of production auditReturnItem in Annex restrictive comment in front of production auditReturnItem in Annex
B.2 (ABNF), rather than just modify it to add exceptions. B.2 (ABNF), rather than just modify it to add exceptions.
skipping to change at line 85 skipping to change at line 85
removed. The need to add extensibility to more productions through removed. The need to add extensibility to more productions through
use of ellipses is noted. use of ellipses is noted.
Section A.2, B.2: the ASN.1 uses three values from contextId Section A.2, B.2: the ASN.1 uses three values from contextId
numbering space to denote NULL, CHOOSE, and ALL. A comment is added numbering space to denote NULL, CHOOSE, and ALL. A comment is added
to the ABNF to reserve the values concerned. to the ABNF to reserve the values concerned.
Section A.2: format of H221NonStandard field does not properly Section A.2: format of H221NonStandard field does not properly
reflect structure of T.35 country code. reflect structure of T.35 country code.
Annex C: changes to ATM-related sections are noted. Annex C: changes to ATM-related sections are noted. Alignment of
sub-octet fields is stated to be at the low-order end of the octet.
Section D.1.3: exponential backoff in the face of congestion made Section D.1.3: exponential backoff in the face of congestion made
mandatory by replacing SHOULD with SHALL. mandatory by replacing SHOULD with SHALL.
Annex E: package serial numbers are revised to make them Annex E: package serial numbers are revised to make them
consecutive. consecutive.
Appendix A step 3: revised to use echo control as defined in the TDM Appendix A step 3: revised to use echo control as defined in the TDM
package. package.
Taylor Standards Track -- Expires Nov 2000 2
3.2 Complete List Of Corrections 3.2 Complete List Of Corrections
Taylor Standards Track -- Expires Nov 2000 2
Section: 2 "References" Section: 2 "References"
---------- ----------
Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661 Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661
(PPP). (PPP).
Editorial: delete unused reference to Q.724. Editorial: delete unused reference to Q.724.
Editorial: Leave Recommendations referred to in Annex C undated, Editorial: Leave Recommendations referred to in Annex C undated,
implying latest issue. implying latest issue.
skipping to change at line 144 skipping to change at line 145
Resolution: Rewrite the first paragraph from the third sentence Resolution: Rewrite the first paragraph from the third sentence
onward, to read: onward, to read:
"Most properties have default values, which are explicitly defined "Most properties have default values, which are explicitly defined
in this standard or in a package (see Section 12) or set by in this standard or in a package (see Section 12) or set by
provisioning. If not provisioned otherwise, all descriptors except provisioning. If not provisioned otherwise, all descriptors except
for TerminationState and LocalControl default to empty/"no value" for TerminationState and LocalControl default to empty/"no value"
when a termination is first created or is returned to the null when a termination is first created or is returned to the null
context. The default contents of the two exceptions are described context. The default contents of the two exceptions are described
in sections 7.1.5 and 7.1.7." in sections 7.1.5 and 7.1.7."
Taylor Standards Track -- Expires Nov 2000 3
Issue: DigitMap entry in table makes explicit reference to DTMF Issue: DigitMap entry in table makes explicit reference to DTMF
tones, but is also intended to apply to other in-band signalling tones, but is also intended to apply to other in-band signalling
systems. systems.
Taylor Standards Track -- Expires Nov 2000 3
Resolution: Change existing text to new one as follows: "Defines Resolution: Change existing text to new one as follows: "Defines
patterns against which sequences of a specified set of events are to patterns against which sequences of a specified set of events are to
be matched so they can be reported as a group rather than singly." be matched so they can be reported as a group rather than singly."
Section: 6.2.5 "Root Termination" Section: 6.2.5 "Root Termination"
---------- ----------
Issue: Root can have statistics as well as properties and events. Issue: Root can have statistics as well as properties and events.
Resolution: add "statistics" to the fourth sentence of the first Resolution: add "statistics" to the fourth sentence of the first
paragraph, listing what is valid for Root. Add "statistics" to what paragraph, listing what is valid for Root. Add "statistics" to what
skipping to change at line 195 skipping to change at line 196
Resolution: Replace the first two sentences (each beginning with the Resolution: Replace the first two sentences (each beginning with the
word "unspecified") with the following text: word "unspecified") with the following text:
"If a required descriptor other than the Audit descriptor is "If a required descriptor other than the Audit descriptor is
unspecified (i.e. entirely absent) from a command, the previous unspecified (i.e. entirely absent) from a command, the previous
values set in that descriptor for that termination, if any, are values set in that descriptor for that termination, if any, are
retained. A missing Audit descriptor is equivalent to an empty retained. A missing Audit descriptor is equivalent to an empty
Audit descriptor. The behaviour of the MG with respect to Audit descriptor. The behaviour of the MG with respect to
unspecified parameters within a descriptor varies with the unspecified parameters within a descriptor varies with the
descriptor concerned, as indicated in succeeding sections." descriptor concerned, as indicated in succeeding sections."
Taylor Standards Track -- Expires Nov 2000 4
Section: 7.1.6 "Stream Descriptor", ABNF (Annex B.2) Section: 7.1.6 "Stream Descriptor", ABNF (Annex B.2)
---------- ----------
Issue: Text indicates use of "true" and "false" values while ABNF Issue: Text indicates use of "true" and "false" values while ABNF
uses "on" and "off" uses "on" and "off"
Taylor Standards Track -- Expires Nov 2000 4
Resolution: Add comment in B.2 that "true" in text corresponds to Resolution: Add comment in B.2 that "true" in text corresponds to
"on" in ABNF, and "false" corresponds to "off". "on" in ABNF, and "false" corresponds to "off".
Section: 7.1.8 "Local and Remote Descriptors" Section: 7.1.8 "Local and Remote Descriptors"
---------- ----------
Issue: case where reserveGroup or reserveValue is true, last Issue: case where reserveGroup or reserveValue is true, last
bulleted item beginning: "If the Mode property of the LocalControl bulleted item beginning: "If the Mode property of the LocalControl
descriptor is RecvOnly or SendRecv,...", could also have DSP descriptor is RecvOnly or SendRecv,...", could also have DSP
involvement in the case of loopback mode. involvement in the case of loopback mode.
skipping to change at line 247 skipping to change at line 248
Signals descriptor to be replaced, as described at the end of this Signals descriptor to be replaced, as described at the end of this
section." section."
Replace "detection" with "recognition" in the fourth paragraph from Replace "detection" with "recognition" in the fourth paragraph from
the end, so that it reads: the end, so that it reads:
"Normally, recognition of an event shall cause any active signals to "Normally, recognition of an event shall cause any active signals to
stop. When KeepActive is specified in the event, the MG shall not stop. When KeepActive is specified in the event, the MG shall not
interrupt any signals active on the Termination on which the event interrupt any signals active on the Termination on which the event
is detected." is detected."
Taylor Standards Track -- Expires Nov 2000 5
In the third-last paragraph, replace all three instances of In the third-last paragraph, replace all three instances of
"detected" with "recognized". "detected" with "recognized".
Leave the word "detected" as is in the final paragraph. Leave the word "detected" as is in the final paragraph.
Taylor Standards Track -- Expires Nov 2000 5
Issue: Case 1, step 2(a) is incorrectly formulated. Existing logic Issue: Case 1, step 2(a) is incorrectly formulated. Existing logic
may result in an infinite loop. Also, the step excludes side effect may result in an infinite loop. Also, the step excludes side effect
actions such as signal termination. actions such as signal termination.
Resolution: Modify step 2(a) to read: Resolution: Modify step 2(a) to read:
"If the event in the queue is in the events listed in the new "If the event in the queue is in the events listed in the new
EventsDescriptor, the MG acts on the event and removes it from the EventsDescriptor, the MG acts on the event and removes it from the
EventBuffer. The time stamp of the Notify shall be the time the EventBuffer. The time stamp of the Notify shall be the time the
event was actually detected. The MG then waits for a new event was actually detected. The MG then waits for a new
EventsDescriptor. While waiting for a new EventsDescriptor, any EventsDescriptor. While waiting for a new EventsDescriptor, any
skipping to change at line 299 skipping to change at line 300
In Annex A.2, make notifyCompletion a BIT STRING with the four In Annex A.2, make notifyCompletion a BIT STRING with the four
cases. In B.2, make it a parameter consisting of a name and a list cases. In B.2, make it a parameter consisting of a name and a list
of values representing the possible completion methods. of values representing the possible completion methods.
Section: 7.1.13 "ServiceChange Descriptor" Section: 7.1.13 "ServiceChange Descriptor"
---------- ----------
Issue: Missing "extension" component in the API. Issue: Missing "extension" component in the API.
Resolution: Add missing component. Resolution: Add missing component.
Taylor Standards Track -- Expires Nov 2000 6
Section: 7.1.14 "DigitMap Descriptor" Section: 7.1.14 "DigitMap Descriptor"
---------- ----------
Editorial: add the following subsections. Editorial: add the following subsections.
7.1.14.1 DigitMap definition, creation, modification and termination 7.1.14.1 DigitMap definition, creation, modification and termination
Taylor Standards Track -- Expires Nov 2000 6
(before first paragraph) (before first paragraph)
7.1.14.2 DigitMap Timers 7.1.14.2 DigitMap Timers
(after the first bullet list) (after the first bullet list)
7.1.14.3 DigitMap syntax 7.1.14.3 DigitMap syntax
(before the long paragraph starting "The formal syntax of the digit (before the long paragraph starting "The formal syntax of the digit
map [...]") map [...]")
7.1.14.4 DigitMap completion event 7.1.14.4 DigitMap completion event
(before the paragraph starting "A digit map is active while the (before the paragraph starting "A digit map is active while the
events descriptor [...]") events descriptor [...]")
7.1.14.5 DigitMap procedures 7.1.14.5 DigitMap procedures
skipping to change at line 348 skipping to change at line 350
Issue: Step 5 in second numbered list understates conditions for Issue: Step 5 in second numbered list understates conditions for
digit map completion when single candidate remains. digit map completion when single candidate remains.
Resolution: Add the words "and it has been fully matched" to the Resolution: Add the words "and it has been fully matched" to the
existing sentence. Also remove the parenthetical remark: existing sentence. Also remove the parenthetical remark:
"... (because the candidate set still contains more than one "... (because the candidate set still contains more than one
alternative event sequence)" alternative event sequence)"
from step 6. from step 6.
Taylor Standards Track -- Expires Nov 2000 7
Issue: Not clear when unmatched events are recognized and trigger Issue: Not clear when unmatched events are recognized and trigger
side effects (e.g. signal termination). side effects (e.g. signal termination).
Resolution: Modify the final sentence of the paragraph following Resolution: Modify the final sentence of the paragraph following
procedural step 6 to read as follows: procedural step 6 to read as follows:
"Normal event behaviour (e.g. stopping of signals unless the digit "Normal event behaviour (e.g. stopping of signals unless the digit
completion event has the KeepActive flag enabled) continues to apply completion event has the KeepActive flag enabled) continues to apply
for each such event detected, except that for each such event detected, except that
Taylor Standards Track -- Expires Nov 2000 7
. the events in the package containing the specified digit map . the events in the package containing the specified digit map
completion event other than the completion event itself are not completion event other than the completion event itself are not
individually notified, and individually notified, and
. an event which triggers a "partial match" completion is not . an event which triggers a "partial match" completion is not
recognized and therefore has no side effects until reprocessed recognized and therefore has no side effects until reprocessed
following the recognition of the digit map completion event." following the recognition of the digit map completion event."
Issue: the last paragraph before the example is misleading if the Issue: the last paragraph before the example is misleading if the
package containing the digit map completion event is different from package containing the digit map completion event is different from
the package containing the actual digits. the package containing the actual digits.
skipping to change at line 400 skipping to change at line 403
AmmRequest ::= SEQUENCE AmmRequest ::= SEQUENCE
{ {
terminationID TerminationIDList, terminationID TerminationIDList,
descriptors SEQUENCE OF AmmDescriptor, descriptors SEQUENCE OF AmmDescriptor,
-- At most one descriptor of each type (see AmmDescriptor) -- At most one descriptor of each type (see AmmDescriptor)
-- allowed in the sequence -- allowed in the sequence
... ...
} }
Taylor Standards Track -- Expires Nov 2000 8
AmmDescriptor ::= CHOICE AmmDescriptor ::= CHOICE
{ {
mediaDescriptor MediaDescriptor, mediaDescriptor MediaDescriptor,
modemDescriptor ModemDescriptor, modemDescriptor ModemDescriptor,
muxDescriptor MuxDescriptor, muxDescriptor MuxDescriptor,
eventsDescriptor EventsDescriptor, eventsDescriptor EventsDescriptor,
eventBufferDescriptor EventBufferDescriptor, eventBufferDescriptor EventBufferDescriptor,
signalsDescriptor SignalsDescriptor, signalsDescriptor SignalsDescriptor,
digitMapDescriptor DigitMapDescriptor, digitMapDescriptor DigitMapDescriptor,
Taylor Standards Track -- Expires Nov 2000 8
auditDescriptor AuditDescriptor, auditDescriptor AuditDescriptor,
... ...
} }
Section: 7.2.3 "Subtract" Section: 7.2.3 "Subtract"
---------- ----------
Issue: cannot use the CHOOSE wildcard for terminationId of a Issue: cannot use the CHOOSE wildcard for terminationId of a
Subtract command. Subtract command.
Resolution: add this qualification to the second sentence, which Resolution: add this qualification to the second sentence, which
skipping to change at line 453 skipping to change at line 457
Resolution: Add the following text: "EventBuffer returns the set of Resolution: Add the following text: "EventBuffer returns the set of
events and associated parameter values currently enabled in the events and associated parameter values currently enabled in the
EventBufferDescriptor." EventBufferDescriptor."
Issue: not clear whether wildcarded context includes the null Issue: not clear whether wildcarded context includes the null
context. context.
Resolution: add statement that ALL as a contextID does not include Resolution: add statement that ALL as a contextID does not include
the null context. the null context.
Taylor Standards Track -- Expires Nov 2000 9
Issue: the text of 7.2.5 allows retrieval of multiple digit maps Issue: the text of 7.2.5 allows retrieval of multiple digit maps
with one AuditValue command if the terminationId is ALL. Moreover, with one AuditValue command if the terminationId is ALL. Moreover,
earlier text in the Annex anticipates that multiple instances of a earlier text in the Annex anticipates that multiple instances of a
descriptor may be returned. The comment in front of production descriptor may be returned. The comment in front of production
auditReturnParameter in Annex B.2 contradicts this text. Note that auditReturnParameter in Annex B.2 contradicts this text. Note that
Annex A has no restriction on the number of instances of any Annex A has no restriction on the number of instances of any
descriptor in either a command or a response. descriptor in either a command or a response.
Taylor Standards Track -- Expires Nov 2000 9
Proposed Resolution: delete the"at-most-once" comment preceding ABNF Proposed Resolution: delete the"at-most-once" comment preceding ABNF
production auditReturnParameter. production auditReturnParameter.
Issue: Does not indicate how an audit of digit maps returns unnamed Issue: Does not indicate how an audit of digit maps returns unnamed
digit maps. digit maps.
Resolution: Change syntax of DigitMapDescriptor to allow return of Resolution: Change syntax of DigitMapDescriptor to allow return of
unnamed digit maps as follows: unnamed digit maps as follows:
digitMapDescriptor = DigitMapToken EQUAL digitMapDescriptor = DigitMapToken EQUAL
skipping to change at line 503 skipping to change at line 507
Proposed Resolution: add the following text in section 7.2.5 after Proposed Resolution: add the following text in section 7.2.5 after
the sentence "This may be useful to get a list of TerminationIDs the sentence "This may be useful to get a list of TerminationIDs
when used with wildcard.": when used with wildcard.":
"Annexes A and B provide a special syntax for presenting such a list "Annexes A and B provide a special syntax for presenting such a list
in condensed form, such that the AuditValue command tag does not in condensed form, such that the AuditValue command tag does not
have to be repeated for each terminationId." have to be repeated for each terminationId."
Also, in the Note at the beginning of section A.2 of Annex A, Also, in the Note at the beginning of section A.2 of Annex A,
provide an exception on the length of type TerminationIdList when provide an exception on the length of type TerminationIdList when
used in contextAuditResult. used in contextAuditResult.
Taylor Standards Track -- Expires Nov 2000 10
Section: 7.2.6 "AuditCapabilities" Section: 7.2.6 "AuditCapabilities"
---------- ----------
Issue: Fails to indicate what AuditCapabilities for Issue: Fails to indicate what AuditCapabilities for
EventBufferDescriptor returns EventBufferDescriptor returns
Resolution: Add the following text: "EventBuffer returns the same Resolution: Add the following text: "EventBuffer returns the same
information as Events." information as Events."
Issue: Inconsistency regarding permissibility of DigitMap or Issue: Inconsistency regarding permissibility of DigitMap or
Packages as capability audit items. Packages as capability audit items.
Taylor Standards Track -- Expires Nov 2000 10
Resolution: Add comment to B.2 "auditItem" production indicating Resolution: Add comment to B.2 "auditItem" production indicating
that DigitMap and Packages are not allowed in the AuditCapabilities that DigitMap and Packages are not allowed in the AuditCapabilities
command. command.
Section: 7.2.8 "ServiceChange" Section: 7.2.8 "ServiceChange"
---------- ----------
Issue: In point 1) describing the Graceful ServiceChange method, the Issue: In point 1) describing the Graceful ServiceChange method, the
scope of the recommendation against new connections is unclear. scope of the recommendation against new connections is unclear.
Resolution: at the end of the first sentence, add the phrase "on the Resolution: at the end of the first sentence, add the phrase "on the
skipping to change at line 556 skipping to change at line 560
Issue: Text for error code 403 should be consistent with that for Issue: Text for error code 403 should be consistent with that for
404 and 405. 404 and 405.
Resolution: Change text to "Syntax error in TransactionRequest" Resolution: Change text to "Syntax error in TransactionRequest"
Issue: There should be no error responses to TransactionReply or Issue: There should be no error responses to TransactionReply or
TransactionPending, lest they create response loops. TransactionPending, lest they create response loops.
Resolution: Delete codes 404, 405, 461-467 Resolution: Delete codes 404, 405, 461-467
Taylor Standards Track -- Expires Nov 2000 11
Section: 8 "Transactions", A.2 Section: 8 "Transactions", A.2
---------- ----------
Issue: state is unclear if a command fails. Issue: state is unclear if a command fails.
Resolution: add the following text: Resolution: add the following text:
"If a command fails, the MG shall as far as possible restore the "If a command fails, the MG shall as far as possible restore the
state which prevailed prior to the attempted execution of the state which prevailed prior to the attempted execution of the
command before continuing with transaction processing." command before continuing with transaction processing."
Section: 8.1.1 "Transaction Identifiers" Section: 8.1.1 "Transaction Identifiers"
Taylor Standards Track -- Expires Nov 2000 11
---------- ----------
Issue: need a transaction identifier to use when reporting a syntax Issue: need a transaction identifier to use when reporting a syntax
error such that the identifier is unavailable. error such that the identifier is unavailable.
Resolution: add text reserving transionId = 0 for this purpose. Resolution: add text reserving transionId = 0 for this purpose.
Section: 8.1.2 "Context Identifiers" Section: 8.1.2 "Context Identifiers"
---------- ----------
Issue: ALL as a context identifier does not include the null Issue: ALL as a context identifier does not include the null
context. context.
skipping to change at line 608 skipping to change at line 613
Section: 11.2 "Cold Start" Section: 11.2 "Cold Start"
---------- ----------
Issue: First paragraph last sentence inadvertently modified -- Issue: First paragraph last sentence inadvertently modified --
duplicates material in 11.3. duplicates material in 11.3.
Resolution: Restore original sentence: "If the MG is unable to Resolution: Restore original sentence: "If the MG is unable to
establish a control relationship with any MGC, it shall wait a establish a control relationship with any MGC, it shall wait a
random amount of time as described in Section 9.2 and then start random amount of time as described in Section 9.2 and then start
contacting its primary, and if necessary, its secondary MGCs again." contacting its primary, and if necessary, its secondary MGCs again."
Taylor Standards Track -- Expires Nov 2000 12
Section: 11.4 "Failure Of an MG" Section: 11.4 "Failure Of an MG"
---------- ----------
Issue: Second para: wrong MG is specified as the one to be used Issue: Second para: wrong MG is specified as the one to be used
after failover. after failover.
Resolution: Change fourth sentence to refer to "secondary MG" rather Resolution: Change fourth sentence to refer to "secondary MG" rather
than "primary MG". than "primary MG".
Section: 12.1.2 "Properties" Section: 12.1.2 "Properties"
Taylor Standards Track -- Expires Nov 2000 12
---------- ----------
Issue: As indicated in 6.2.4, Properties occur in other descriptors Issue: As indicated in 6.2.4, Properties occur in other descriptors
besides LocalControl and TerminationState. besides LocalControl and TerminationState.
Resolution: after the sentence mentioning TerminationState, add Resolution: after the sentence mentioning TerminationState, add
another sentence: another sentence:
"Although these are the most common cases, it is also possible for a "Although these are the most common cases, it is also possible for a
property to be defined for other descriptors." property to be defined for other descriptors."
Section: 12.1.4 "Signals" Section: 12.1.4 "Signals"
skipping to change at line 662 skipping to change at line 668
Annex B.2 indicating that these values are reserved. Annex B.2 indicating that these values are reserved.
Section: Annex A.2, ASN.1 Syntax Section: Annex A.2, ASN.1 Syntax
---------- ----------
Issue: sloppy ASN.1 -- in production EventBufferControl the values Issue: sloppy ASN.1 -- in production EventBufferControl the values
"off" and "lockstep" should not be capitalized, and IA5STRING in "off" and "lockstep" should not be capitalized, and IA5STRING in
production NonStandardIdentifier should be IA5String. Both production NonStandardIdentifier should be IA5String. Both
TransactionID and TransactionId are used. A number of productions TransactionID and TransactionId are used. A number of productions
need ellipses to express extensibility. need ellipses to express extensibility.
Taylor Standards Track -- Expires Nov 2000 13
Resolution: fix them. Resolution: fix them.
Taylor Standards Track -- Expires Nov 2000 13
Issue: syntax for PropertyParm does not support sub-lists (i.e. Issue: syntax for PropertyParm does not support sub-lists (i.e.
parameters supporting multiple values simultaneously) parameters supporting multiple values simultaneously)
Resolution: add a third choice to extrainfo in PropertyParm as Resolution: add a third choice to extrainfo in PropertyParm as
follows: follows:
extraInfo CHOICE extraInfo CHOICE
{ {
relation Relation, relation Relation,
range BOOLEAN, range BOOLEAN,
sublist BOOLEAN sublist BOOLEAN
skipping to change at line 816 skipping to change at line 822
were sent." were sent."
Section: Annex D.1.1 "Providing At-Most-Once Functionality" Section: Annex D.1.1 "Providing At-Most-Once Functionality"
---------- ----------
Issue: Second para last sentence provides a procedural reference to Issue: Second para last sentence provides a procedural reference to
8.2.3. Should refer to UDP-specific procedures. 8.2.3. Should refer to UDP-specific procedures.
Resolution: Add reference to D.1.4. Resolution: Add reference to D.1.4.
Taylor Standards Track -- Expires Nov 2000 16 Taylor Standards Track -- Expires Nov 2000 16
Section: Annex D.1.4 "Provisional responses"
----------
Issue: First paragraph, last sentence talks about when to send the
Transaction Pending response. When UDP/ALF is in use, the
originator of a transaction may repeat it because it has not
received an acknowledgement that the transaction was received. An
appropriate response to a duplicate transaction which is still being
processed is to return Transaction Pending.
Resolution: Add the sentence: "They SHOULD send this response if
they receive a repetition of a transaction that is still being
executed."
Issue: Second para: transaction originator may not have received
TransactionPending response(s) because they were lost, and may
therefore not know that responder is expecting immediate
acknowledgement of the TransactionReply.
Resolution: add an optional field to TransactionReply allowing the
responder to indicate if an immediate ACK is required. Add text in
the section indicating that when the responder has sent a
provisional response, it shall also set the indicator in the final
transaction reply to indicate that an immediate acknowledgement is
required.
Section: Annex D.1.3 "Repeating Requests, Responses and Section: Annex D.1.3 "Repeating Requests, Responses and
Acknowledgements" Acknowledgements"
---------- ----------
Issue: Make exponential backoff in the face of congestion mandatory. Issue: Make exponential backoff in the face of congestion mandatory.
Resolution: To the paragraph just before the note, which begins "The Resolution: To the paragraph just before the note, which begins "The
specification purposely avoids specifying any value for the specification purposely avoids specifying any value for the
retransmission timers...", add the following sentence: retransmission timers...", add the following sentence:
" Implementations SHALL ensure that the algorithm used to calculate "Implementations SHALL ensure that the algorithm used to calculate
retransmission timing includes an exponentially increasing component retransmission timing performs an exponentially increasing backoff
to provide appropriate behaviour in the face of congestion." of the retransmission timeout for each retransmission or repetition
after the first one."
In the paragraph in the middle of the note beginning "After any In the paragraph in the middle of the note beginning "After any
retransmission ...", capitalize the word SHOULD to emphasize the retransmission ...", capitalize the word SHOULD to emphasize the
importance of the steps which follow. importance of the steps which follow.
Issue: Last paragraph is equivocal about what ServiceChangeReason to Issue: Last paragraph is equivocal about what ServiceChangeReason to
use when recovering from loss of contact; it must always be use when recovering from loss of contact; it must always be
"Disconnected". "Disconnected".
Resolution: Change the two sentences following the phrase "_ and it Resolution: Change the two sentences following the phrase "_ and it
begins its recovery process" to read as follows: "The MG shall use a begins its recovery process" to read as follows: "The MG shall use a
ServiceChange with ServiceChangeMethod set to disconnected so that ServiceChange with ServiceChangeMethod set to disconnected so that
the new MGC will be aware that the MG lost one or more the new MGC will be aware that the MG lost one or more
transactions." transactions."
Section: Annex D.1.4 "Provisional responses"
----------
Issue: First paragraph, last sentence talks about when to send the
Transaction Pending response. When UDP/ALF is in use, the
originator of a transaction may repeat it because it has not
received an acknowledgement that the transaction was received. An
appropriate response to a duplicate transaction which is still being
processed is to return Transaction Pending.
Resolution: Add the sentence: "They SHOULD send this response if
they receive a repetition of a transaction that is still being
executed."
Issue: Second para: transaction originator may not have received
TransactionPending response(s) because they were lost, and may
therefore not know that responder is expecting immediate
acknowledgement of the TransactionReply.
Resolution: add an optional field to TransactionReply allowing the
responder to indicate if an immediate ACK is required. Add text in
the section indicating that when the responder has sent a
provisional response, it shall also set the indicator in the final
Taylor Standards Track -- Expires Nov 2000 17 Taylor Standards Track -- Expires Nov 2000 17
transaction reply to indicate that an immediate acknowledgement is
required.
Section: Annex E "Basic Packages" Section: Annex E "Basic Packages"
---------- ----------
Issue: package numbering does not follow order of presentation. Issue: package numbering does not follow order of presentation.
Resolution: renumber packages to follow order of numbering. Resolution: renumber packages to follow order of numbering.
Section: Annex E.2.1 "Base Root Package -- Properties" Section: Annex E.2.1 "Base Root Package -- Properties"
---------- ----------
Issue: the descriptor in which these properties occur is not Issue: the descriptor in which these properties occur is not
specified. specified.
 End of changes. 35 change blocks. 
50 lines changed or deleted 58 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/