Spreadsheet: f8b5e84f-c8e6-4f8b-b966-3d20da0a69d9
Sheet: Sheet1

Unnamed: 0 | INSTRUCTIONS: Use this form to enter your comments.  When complete, save the file on your hard drive and attach this file as instructed  to the SIPforum ua-config list.  Section Number  - Required.    Current/Proposed Text- Comment - These fields are required.  Enter your comment and proposed change in these fields, respectively.  Use plain text characters only.  Required for Approval ?  - This field is required.  If you have already voted Negative (Disapprove), the data will be associated with your Negative (Disapprove) vote.  This categorization is used to differentiate those comments submitted as part of your Negative (Disapprove) vote from other comments that you may wish to submit. Only those comments that have a "Yes" in the "Required for Approval" box will be considered as part of your negative vote. If you have already voted Affirmative (Approve), the "Required for Approval" data will not be used. | Unnamed: 2 | Unnamed: 3 | Unnamed: 4 | Unnamed: 5 | Unnamed: 6 | Unnamed: 7 | Unnamed: 8
Author | Section Number | Current Text | Proposed Text | Comment | Required for approval?    (enter Yes or No) | Technical or editorial | Notes | Resolution
Sumanth | 2.6 | The conﬁguration data stored by a UA is considered valid so long as the UA has a subscription to the CS as described in Section 2.5.1. | The conﬁguration data stored by a UA is considered valid so long as the UA has not obtain updated information (e.g., when it obtained configuration, or via a NOTIFY message). | There may be cases where you don't want to maintain an active subscription (e.g., a one-time configuration to a new device that has not been associated with a subscription as yet). So requiring a subscription may not really be a good idea. | No, although I would appreciate a good reason as to why this can't be done (if I am missing something here). | T | It was found that the concern could be addressed sufficiently by making changes to 2.5.1.2 to remove the requirement for expires with value zero. | Accepted with modification
Marek Dutkiewicz | 2.1.2 |  | Please add text to cover the method by which the DNS address is discovered in an IPv6 network. It does not utilize DHCP, but has some form of discovery from the router. | IPv6 will is already being deployed and will increasingly be deployed so it is important that this document consider the needs of IPv6. | Yes | T | New text added for IPv6 | Accepted
Marek Dutkiewicz | 2.3 |  |  | There will be situations in which a user agent is required to obtain configuration from more than one source. E.g. Telephony configuration from a VoIP Service provider and presence subscription information from a hosted presence server. Since these may not be under control of the same entity it would be helpful to be able to set up more than one Configuration Service subscription. I recognize this is 'out of scope' for this revision of the UA Config recommendations but encourage the working group to consider this for any future revisions of the UA Config recommendations. | No | T |  | Noted for future
Marek Dutkiewicz | 3.1 |  |  | I would have preferred to have seen a common format defined for the format of the data in this section. Utilizing a common format between all user agents would simplify the implementation of the Configuration Service. | No | T |  | Noted for future
mhp | 1.3. | "narative" "naratives" | "narrative" and "narratives" | typo |  | E |  | Accepted
mhp | 2.1. | "An UA" | "A UA" | [NAME] para 2 |  | E |  | Accepted
mhp | 2.3.1 | "SFUA:CS" | "SFUA:CFG" | As per later paragraphs and draft |  | E |  | Accepted
mhp | 2.4. | "a URI constructed" | "a URL constructed" | Rest of document uses URL not URI |  | E |  | Accepted
mhp | 2.4. | "The UA MUST store all..." | "The UA MUST retain all..." | Don't think we require storage across reboots (for example) here, just to keep a copy for later use.  "Retain" doesn't have the same persistence connotations as "store" for me. |  | E |  | Accepted
mhp | 2.5.1.2 | "attempt to obtain new configuration  data as specified in Section 2.4.2" | "attempt to revalidate it as specified in Section 2.6" | Section 2.4.2 concerns HTTP failures and doesn't address this.  Section 2.6 does. |  | E |  | Accepted
mhp | 2.5.2 | "data it stored" | "data it retained" | See comment on 2.4 |  | E |  | Accepted
mhp | 2.7. | "preceeding" | "preceding" | typo |  | E |  | Accepted