Dear all,
I see that after my renewal of the draft only some comments were given.
We see this as an important issue to keep interoperability between PSTN and SIP networks.

Meanwhile there is also a request on putting a Reason Header within a 183 Progress due to the fact that it is possible to put a Q.850 cause value within an ACM including an indication that an announcement is played.

This case would be valuable for a PSTN - SIP -PSTN passing without any use of SIP-T.

The main used case is to put the Reason Header within 4xx, 5xx, 6xx and 199 to send an specific indication either back into an other PSTN or an Application Server that can put an announcement into the path based on the ISUP cause.

But nevertheless I Would like to see this draft on the agenda and at least as an Woki Item within DISPATCH.

Best regards

Roland  

-----Ursprüngliche Nachricht-----
Von: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] Im Auftrag von Mary Barnes
Gesendet: Donnerstag, 1. Oktober 2009 15:56
An: dispatch@ietf.org
Betreff: [dispatch] DISPATCH IETF-76 plans

Hi all, 

Per Gonzalo's reminder on Sept. 16th, charter proposals for the topics
to be handled/dispatched prior to and at IETF-76 were due on Sept. 21st.
The following summarizes the status of the topics that had been
previously put forth - both prior to Sept. 7th deadline and up through
the 21st. Obviously, we have to balance interest and willingness to
contribute to the work (based on mailing list discussions) with the fact
that some folks were more conscientious in meeting the deadlines. 

We received charter proposals (problem statements/deliverables) for the
following, with the current status highlighted.  

o Overload (received prior to Sept. 16th) - separate mailing list setup.
Needs more discussion. 

o CBUS: some good discussion on problem statement. Needs more
discussion.

o Session recording: updated charter proposal based on IETF-75 feedback.
Need more WG feedback. Is this ready?  

o Disaggregated media: Good level of interest 

o SIP - XMPP:  High level of WG interest. Propose a separate Mailing
list and Adhoc at IETF-76. 

o Alert-info URNs: Good level of interest. 

o NGN Reason: Some interest. Needs more discussion and scoping. 

The above items are the current targets for IETF-76 discussions.  Based
on those discussions, agenda time will be allocated, items dispatched
and adhocs scheduled as appropriate. Note, that the minimum time we
would allocate to a topic is 30 minutes and some may warrant 45 minutes.
If we schedule adhocs, we will try to have those announced around the
time the agenda is finalized. 

As a reminder, the following are the cutoffs for drafts, so please make
sure that any drafts relevant to the topic are submitted prior to those
deadlines:
* - 00 documents:  Oct. 19th (just over 2 weeks)
* all other documents: Oct. 26th (just over 3 weeks)

Please keep in mind that the focus of discussions should be the problem
statement, scope and proposed deliverables for the topic.    

We did not receive charter proposals for the following. The current
status is summarized:
o Third-party authorization: Pre-IETF-75 problem statement had some
discussion. But, no discussion since that time. 
o Identity: Document available. Need further discussion and WG feedback
to refine requirements, problem statement, scope and
deliverables/milestones. 
o Domain registrations in SIP: Problem statement posted, but no
deliverables/milestones or document. 
o Reference to an earlier communication: Problem statement posted, but
no deliverables/milestones or document. 

As a reminder, items can be dispatched without being discussed at a f2f
meeting and the most effective way to achieve this is to have problem
statements, scope of topics and any relevant documents available early
enough for the WG to provide feedback - i.e., you do not have to wait
for the pre-meeting deadlines, which are more in the way of drop dead
dates than optimal dates.  

Please, let the chairs know if there are any concerns.

Thanks,
Mary Barnes
DISPATCH WG co-chair
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch