Subject: Re: [Atoca] Meeting minutes?
From: [email-masked] (Scott O. Bradner)
To: [email-masked], [email-masked]
Date: Wed, 24 Nov 2010 13:02:50 -0500 (EST)
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <earlywarning.ietf.org>

working on them

Scott

----
>From [email-masked]  Wed Nov 24 03:36:21 2010
From: Hannes Tschofenig <[email-masked]>
Date: Wed, 24 Nov 2010 10:36:13 +0200
To: [email-masked]
Subject: [Atoca] Meeting minutes?
Sender: [email-masked]

Hi all, 

I wanted to look at the meeting minutes remembering that there were some additional requirements to take into consideration. 
I could not find them in the proceedings. 

Ciao
Hannes

_______________________________________________
earlywarning mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/earlywarning

From: Hannes Tschofenig <[email-masked]>
Date: Wed, 24 Nov 2010 10:44:19 +0200
To: [email-masked]
Subject: [Atoca] Next version of draft-ietf-atoca-requirements

Hi all,=20

when we put the slides together for the Beijing IETF meeting we noticed =
the story we created for the slide set was actually better than the one =
we have currently in the document (from a structural point of view). I =
got the impression that the ATOCA presentation was well received.

In particular, we have the following two steps that are important for =
this working group:

1.Explicit or implicit Subscription
   =96Explicit subscription via <draft-rosen-sipping-cap-05.txt>  or via =
the corresponding XMPP mechanism
   =96Implicit subscription by being located in a specific area.
2.Alert Delivery
   =96Conveying alert via CAP message

The architectural figure focuses on item #2 and a clarification would be =
useful.=20

We would call out these two steps explicitly (instead of the current =
wording on "Alert Push Communication" and "Alert Subscription =
Communication" wording).=20

We would like to make these ***editorial changes*** with the next update =
(unless there are objections) to improve readability.

Ciao
Hannes
(on behalf other author's team)=

From: Hannes Tschofenig <[email-masked]>
Date: Wed, 24 Nov 2010 10:36:13 +0200
To: [email-masked]
Subject: [Atoca] Meeting minutes?

Hi all,=20

I wanted to look at the meeting minutes remembering that there were some =
additional requirements to take into consideration.=20
I could not find them in the proceedings.=20

Ciao
Hannes

Date: Fri, 12 Nov 2010 23:38:38 -0000
From: "Mark Wood" <[email-masked]>
To: "DRAGE, Keith (Keith)" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Subject: [Atoca] EU-ALERT
Reply-To: [email-masked]

------=_20101112233838_49798
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Gents

For you kind consideration, here is a copy of the ETSI EU alert document.

Mark

------=_20101112233838_49798
Content-Type: application/pdf; name="EU-Alert.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="EU-Alert.pdf"

------=_20101112233838_49798--

Date: Fri, 12 Nov 2010 23:52:35 +0800
From: "Richard L. Barnes" <[email-masked]>
To: "Thomson, Martin" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [Atoca] Consensus call for adoption of	draft-schulzrinne-atoca-requirements

I have read this draft and believe it is a good starting point for this 
working group's requirements.  I support its adoption.
--Richard

On 11/12/10 5:04 PM, Thomson, Martin wrote:
> We would like to confirm the indication of the meeting participants on the adoption of draft-schulzrinne-atoca-requirements to the ATOCA working group.
>
> Please send a reply to this email indicating whether we should adopt or not adopt this draft.
>
> A significant number of participants at the meeting indicated their support for this document as a working group document.  There was no opposition.
>
> This 2 week call ends on the 26th of November.
>
> --Martin&  Scott
> _______________________________________________
> earlywarning mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/earlywarning

Content-class: urn:content-classes:message
Date: Fri, 12 Nov 2010 03:30:05 -0800
From: "Roger Marshall" <[email-masked]>
To: "Thomson, Martin" <[email-masked]>, <[email-masked]>
Subject: Re: [Atoca] Consensus call for adoption ofdraft-schulzrinne-atoca-requirements

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB825D.1EAD6349
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes.  I support adoption as a wg item.
=20
-roger marshall.

________________________________

From: [email-masked] on behalf of Thomson, Martin
Sent: Fri 11/12/2010 1:04 AM
To: [email-masked]
Subject: [Atoca] Consensus call for adoption ofdraft-schulzrinne-atoca-requ=
irements

We would like to confirm the indication of the meeting participants on the =
adoption of draft-schulzrinne-atoca-requirements to the ATOCA working group.

Please send a reply to this email indicating whether we should adopt or not=
 adopt this draft.

A significant number of participants at the meeting indicated their support=
 for this document as a working group document.  There was no opposition.

This 2 week call ends on the 26th of November.

--Martin & Scott
_______________________________________________
earlywarning mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/earlywarning

CONFIDENTIALITY NOTICE: The information contained in this message may be pr=
ivileged and/or confidential. If you are not the intended recipient, or res=
ponsible for delivering this message to the intended recipient, any review,=
 forwarding, dissemination, distribution or copying of this communication o=
r any attachment(s) is strictly prohibited. If you have received this messa=
ge in error, please notify the sender immediately, and delete it and all at=
tachments from your computer and network.

------_=_NextPart_001_01CB825D.1EAD6349
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[Atoca] Consensus call for adoption ofdraft-sc=
hulzrinne-atoca-requirements</TITLE>
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18975"></HEAD>
<BODY>
<DIV dir=3Dltr id=3DidOWAReplyText67842>
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Yes.&nbsp; I sup=
port adoption as a wg item.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>-roger marshall.</FONT></DIV></D=
IV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> [email-masked] on =
behalf of Thomson, Martin<BR><B>Sent:</B> Fri 11/12/2010 1:04 AM<BR><B>To:<=
/B> [email-masked]<BR><B>Subject:</B> [Atoca] Consensus call for ado=
ption ofdraft-schulzrinne-atoca-requirements<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>We would like to confirm the indication of the meeting pa=
rticipants on the adoption of draft-schulzrinne-atoca-requirements to the A=
TOCA working group.<BR><BR>Please send a reply to this email indicating whe=
ther we should adopt or not adopt this draft.<BR><BR>A significant number o=
f participants at the meeting indicated their support for this document as =
a working group document.&nbsp; There was no opposition.<BR><BR>This 2 week=
 call ends on the 26th of November.<BR><BR>--Martin &amp; Scott<BR>________=
_______________________________________<BR>earlywarning mailing list<BR>ear=
[email-masked]<BR><A href=3D"https://www.ietf.org/mailman/listinfo/earl=
ywarning">https://www.ietf.org/mailman/listinfo/earlywarning</A><BR></FONT>=
</P></DIV>
<p><span style=3D"font-family:'Arial';font-size:8pt;">CONFIDENTIALITY NOTIC=
E: The information contained in this message may be privileged and/or confi=
dential. If you are not the intended recipient, or responsible for deliveri=
ng this message to the intended recipient, any review, forwarding, dissemin=
ation, distribution or copying of this communication or any attachment(s) i=
s strictly prohibited. If you have received this message in error, please n=
otify the sender immediately, and delete it and all attachments from your c=
omputer and network.</span></p></BODY></HTML>

------_=_NextPart_001_01CB825D.1EAD6349--

From: "Thomson, Martin" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 12 Nov 2010 17:04:45 +0800
Accept-Language: en-US
acceptlanguage: en-US
Subject: [Atoca] Consensus call for adoption of draft-schulzrinne-atoca-requirements

From: "DRAGE, Keith (Keith)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 12 Nov 2010 07:05:41 +0100
Accept-Language: en-US
acceptlanguage: en-US
Subject: Re: [Atoca] Document link to 3GPP PWS specifications

--_000_EDC0A1AE77C57744B664A310A0B23AE21E03AD49FRMRSSXCHMBSC3d_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The following link also provides a slightly different way into the same dat=
a:

http://www.3gpp.org/ftp/Specs/html-info/status-report.htm

regards

Keith

________________________________
From: [email-masked] [mailto:[email-masked]] =
On Behalf Of [email-masked]
Sent: Friday, November 12, 2010 5:59 AM
To: [email-masked]
Subject: [Atoca] Document link to 3GPP PWS specifications

Dear ATOCA,

I got a question today on the availability of the 3GPP specifications that =
I referenced to in my presentation. All 3GPP specifications are available f=
or download over here, just pick your favourite release and specification s=
eries: http://www.3gpp.org/ftp/Specs/latest/

Also historical versions are provided, but that link points to the latest a=
vailable versions.

Apologies for not including the link in the presentation.

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724

--_000_EDC0A1AE77C57744B664A310A0B23AE21E03AD49FRMRSSXCHMBSC3d_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR><!-- converted fro=
m rtf -->
<STYLE>.EmailQuote {
	PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt; BORDER-LEFT: #800000 2px solid
}
</STYLE>
</HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The following link also provides a slightly differ=
ent way=20
into the same data:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><A=20
href=3D"http://www.3gpp.org/ftp/Specs/html-info/status-report.htm">http://w=
ww.3gpp.org/ftp/Specs/html-info/status-report.htm</A></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995470406-12112010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Keith</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> [email-masked]=20
  [mailto:[email-masked]] <B>On Behalf Of=20
  </B>[email-masked]<BR><B>Sent:</B> Friday, November 12, 2010 =
5:59=20
  AM<BR><B>To:</B> [email-masked]<BR><B>Subject:</B> [Atoca] Documen=
t=20
  link to 3GPP PWS specifications<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3D"Arial, sans-serif" size=3D2>
  <DIV>Dear ATOCA,</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I got a question today on the availability of the 3GPP specification=
s=20
  that I referenced to in my presentation. All 3GPP specifications are avai=
lable=20
  for download over here, just pick your favourite release and specificatio=
n=20
  series: <A href=3D"http://www.3gpp.org/ftp/Specs/latest/"><FONT=20
  color=3D#0000ff><U>http://www.3gpp.org/ftp/Specs/latest/</U></FONT></A></=
DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Also historical versions are provided, but that link points to the l=
atest=20
  available versions.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Apologies for not including the link in the presentation.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>BR,</DIV>
  <DIV>Hannu Hietalahti</DIV>
  <DIV>3GPP TSG CT Chairman</DIV>
  <DIV>tel: +358 40 5021724</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></FONT></BODY></HTML>

--_000_EDC0A1AE77C57744B664A310A0B23AE21E03AD49FRMRSSXCHMBSC3d_--

From: <[email-masked]>
To: <[email-masked]>
Date: Fri, 12 Nov 2010 06:59:20 +0100
Accept-Language: en-US
acceptlanguage: en-US
Subject: [Atoca] Document link to 3GPP PWS specifications

--_000_5BAF85033CB5F3439C4DE153165522B1109FFC5416NOKEUMSG06mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear ATOCA,

I got a question today on the availability of the 3GPP specifications that =
I referenced to in my presentation. All 3GPP specifications are available f=
or download over here, just pick your favourite release and specification s=
eries: http://www.3gpp.org/ftp/Specs/latest/

Also historical versions are provided, but that link points to the latest a=
vailable versions.

Apologies for not including the link in the presentation.

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724

--_000_5BAF85033CB5F3439C4DE153165522B1109FFC5416NOKEUMSG06mgd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Dear ATOCA,</div>
<div>&nbsp;</div>
<div>I got a question today on the availability of the 3GPP specifications =
that I referenced to in my presentation. All 3GPP specifications are availa=
ble for download over here, just pick your favourite release and specificat=
ion series: <a href=3D"http://www.3gpp.org/ftp/Specs/latest/"><font color=
=3D"#0000FF"><u>http://www.3gpp.org/ftp/Specs/latest/</u></font></a></div>
<div>&nbsp;</div>
<div>Also historical versions are provided, but that link points to the lat=
est available versions.</div>
<div>&nbsp;</div>
<div>Apologies for not including the link in the presentation.</div>
<div>&nbsp;</div>
<div>BR,</div>
<div>Hannu Hietalahti</div>
<div>3GPP TSG CT Chairman</div>
<div>tel: &#43;358 40 5021724</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_5BAF85033CB5F3439C4DE153165522B1109FFC5416NOKEUMSG06mgd_--

Date: Fri, 12 Nov 2010 13:15:13 +0800
From: Peter Saint-Andre <[email-masked]>
To: [email-masked]
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Subject: Re: [Atoca] Jabber room?

This is a cryptographically signed message in MIME format.

--------------ms030407020305000703090609
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Perhaps the room had not yet been created because this is a new WG. I
was able to join the room just now.

xmpp:[email-masked]?join

On 11/12/10 12:56 PM, Janet P Gunn wrote:
>=20
> When I try to get into the atoca jabber room I get "403: forbidden".
>=20
> Am I doing something wrong, or is there a problem with jabber?
>=20
> Janet
>=20

--------------ms030407020305000703090609
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

AAAA
--------------ms030407020305000703090609--

To: [email-masked], [email-masked]
Date: Fri, 12 Nov 2010 00:07:38 -0500 (EST)
From: [email-masked] (Scott O. Bradner)
Subject: Re: [Atoca] Jabber chat room for meeting is not working for me

fixed

Scott

---
f

To: Cullen Jennings <[email-masked]>
From: Janet P Gunn <[email-masked]>
Date: Fri, 12 Nov 2010 00:02:57 -0500
Cc: [email-masked], [email-masked]
Subject: Re: [Atoca] Jabber chat room for meeting is not working for me

This is a multipart message in MIME format.
--=_alternative 001BC064852577D9_=
Content-Type: text/plain; charset="US-ASCII"

OK.

[email-masked] wrote on 11/11/2010 11:58:07 PM:

> [image removed] 
> 
> [Atoca] Jabber chat room for meeting is not working for me
> 
> Cullen Jennings 
> 
> to:
> 
> earlywarning
> 
> 11/11/2010 11:57 PM
> 
> Sent by:
> 
> [email-masked]
> 
> 
> The atoca room does not seem to allow me folks to join. I suggest we
> just use the [email-masked] chat room
> 
> Cullen
> 
> _______________________________________________
> earlywarning mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/earlywarning

--=_alternative 001BC064852577D9_=
Content-Type: text/html; charset="US-ASCII"

<br><font size=2 face="sans-serif"><br>
<br>
OK.</font>
<br>
<br><tt><font size=2>[email-masked] wrote on 11/11/2010
11:58:07 PM:<br>
<br>
&gt; [image removed] </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; [Atoca] Jabber chat room for meeting is not working for me</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Cullen Jennings </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; to:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; earlywarning</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; 11/11/2010 11:57 PM</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Sent by:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; [email-masked]</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; The atoca room does not seem to allow me folks to join. I suggest
we<br>
&gt; just use the [email-masked] chat room<br>
&gt; <br>
&gt; Cullen<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; earlywarning mailing list<br>
&gt; [email-masked]<br>
&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/earlywarning><tt><font size=2>https://www.ietf.org/mailman/listinfo/earlywarning</font></tt></a><tt><font size=2><br>
</font></tt>
--=_alternative 001BC064852577D9_=--

From: Cullen Jennings <[email-masked]>
Date: Thu, 11 Nov 2010 21:58:07 -0700
To: [email-masked]
Subject: [Atoca] Jabber chat room for meeting is not working for me

The atoca room does not seem to allow me folks to join. I suggest we =
just use the [email-masked] chat room

Cullen

To: [email-masked], [email-masked]
From: Janet P Gunn <[email-masked]>
Date: Thu, 11 Nov 2010 23:56:52 -0500
Subject: [Atoca]  Jabber room?

This is a multipart message in MIME format.
--=_alternative 001B31CD852577D9_=
Content-Type: text/plain; charset="US-ASCII"

When I try to get into the atoca jabber room I get "403: forbidden".

Am I doing something wrong, or is there a problem with jabber?

Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to 
any order or other contract unless pursuant to explicit written agreement 
or government initiative expressly permitting the use of e-mail for such 
purpose.
--=_alternative 001B31CD852577D9_=
Content-Type: text/html; charset="US-ASCII"

<br><font size=2 face="sans-serif">When I try to get into the atoca jabber
room I get &quot;403: forbidden&quot;.</font>
<br>
<br><font size=2 face="sans-serif">Am I doing something wrong, or is there
a problem with jabber?</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. <br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.</font>
--=_alternative 001B31CD852577D9_=--

From: <[email-masked]>
To: <[email-masked]>
Date: Thu, 11 Nov 2010 08:59:29 +0100
Accept-Language: en-US
acceptlanguage: en-US
Cc: [email-masked]
Subject: Re: [Atoca] Agenda update

Understood.

Thanks for your guidance.

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724
=20

>-----Original Message-----
>From: ext Thomson, Martin [mailto:[email-masked]]=20
>Sent: 10 November, 2010 08:19
>To: Hietalahti Hannu (Nokia-CIC/Oulu)
>Cc: [email-masked]
>Subject: RE: [Atoca] Agenda update
>
>Hi Hannu,
>
>In these presentations, I find that it helps to leave a=20
>generous portion of the time for questions.  Use your=20
>judgement :)  Maybe 5 minutes.
>
>Your presentation has a fair bit of content.  I expect that we=20
>wont have time to get into all of the details.  We can leave=20
>the details for people to look into on their own. =20
>
>Getting the big picture is most important at this stage. =20
>We've all done this sort of stuff before, we can look up the=20
>specifications at our leisure later :)
>
>Hope that helps,
>Martin
>
>On 2010-11-10 at 14:03:13, [email-masked] wrote:
>> Thanks Martin,
>>=20
>> OK for me. My presentation is flexible as my intention was=20
>not to start
>> a walkthrough of the call flows.
>>=20
>> Any idea whether I should leave some time for questions and=20
>discussion?
>>=20
>> BR,
>> Hannu Hietalahti
>> 3GPP TSG CT Chairman
>> tel: +358 40 5021724
>>=20
>>=20
>> >-----Original Message-----
>> >From: [email-masked]
>> >[mailto:[email-masked]] On Behalf Of ext
>> >Richard L. Barnes
>> >Sent: 10 November, 2010 03:19
>> >To: Thomson, Martin
>> >Cc: [email-masked]
>> >Subject: Re: [Atoca] Agenda update
>> >
>> >For the reader's convenience, a link to XEP-0127:
>> ><http://xmpp.org/extensions/xep-0127.html>
>> >
>> >
>> >
>> >On 11/10/10 8:03 AM, Thomson, Martin wrote:
>> >> I've updated the agenda for the meeting on Friday.
>> >>
>> >> Joe Hildebrand has offered to do a very short presentation
>> >on the capabilities of XMPP that might be applicable to our
>> >work.  XMPP already supports conveyance of CAP alerts (see XEP 127).
>> >>
>> >> --
>> >>
>> >> 5 min - note well, bash - Chairs
>> >> 15 min - status, overview - Chairs
>> >>
>> >> Overview of related work
>> >> 20 min - 3GPP - Hannu Hietalahti
>> >> 10 min - XMPP - Joe Hildebrand
>> >>
>> >> Requirements discussion
>> >> 20 min - draft-ietf-atoca-requirements - Hannes Tschofenig
>> >> 20 min - draft-ietf-atoca-cap - Hannes Tschofenig
>> >>
>> >> --Martin
>> >> _______________________________________________
>> >> earlywarning mailing list
>> >> [email-masked]
>> >> https://www.ietf.org/mailman/listinfo/earlywarning
>> >_______________________________________________
>> >earlywarning mailing list
>> >[email-masked]
>> >https://www.ietf.org/mailman/listinfo/earlywarning
>> >
>
>
>=

From: "Thomson, Martin" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Wed, 10 Nov 2010 14:18:51 +0800
Accept-Language: en-US
acceptlanguage: en-US
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [Atoca] Agenda update

From: <[email-masked]>
To: <[email-masked]>, <[email-masked]>
Date: Wed, 10 Nov 2010 07:03:13 +0100
Accept-Language: en-US
acceptlanguage: en-US
Cc: [email-masked]
Subject: Re: [Atoca] Agenda update

Thanks Martin,

OK for me. My presentation is flexible as my intention was not to start a w=
alkthrough of the call flows.

Any idea whether I should leave some time for questions and discussion?

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724
=20

>-----Original Message-----
>From: [email-masked]=20
>[mailto:[email-masked]] On Behalf Of ext=20
>Richard L. Barnes
>Sent: 10 November, 2010 03:19
>To: Thomson, Martin
>Cc: [email-masked]
>Subject: Re: [Atoca] Agenda update
>
>For the reader's convenience, a link to XEP-0127:
><http://xmpp.org/extensions/xep-0127.html>
>
>
>
>On 11/10/10 8:03 AM, Thomson, Martin wrote:
>> I've updated the agenda for the meeting on Friday.
>>
>> Joe Hildebrand has offered to do a very short presentation=20
>on the capabilities of XMPP that might be applicable to our=20
>work.  XMPP already supports conveyance of CAP alerts (see XEP 127).
>>
>> --
>>
>> 5 min - note well, bash - Chairs
>> 15 min - status, overview - Chairs
>>
>> Overview of related work
>> 20 min - 3GPP - Hannu Hietalahti
>> 10 min - XMPP - Joe Hildebrand
>>
>> Requirements discussion
>> 20 min - draft-ietf-atoca-requirements - Hannes Tschofenig
>> 20 min - draft-ietf-atoca-cap - Hannes Tschofenig
>>
>> --Martin
>> _______________________________________________
>> earlywarning mailing list
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/earlywarning
>_______________________________________________
>earlywarning mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/earlywarning
>=

Date: Wed, 10 Nov 2010 09:19:18 +0800
From: "Richard L. Barnes" <[email-masked]>
To: "Thomson, Martin" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [Atoca] Agenda update

For the reader's convenience, a link to XEP-0127:
<http://xmpp.org/extensions/xep-0127.html>

On 11/10/10 8:03 AM, Thomson, Martin wrote:
> I've updated the agenda for the meeting on Friday.
>
> Joe Hildebrand has offered to do a very short presentation on the capabilities of XMPP that might be applicable to our work.  XMPP already supports conveyance of CAP alerts (see XEP 127).
>
> --
>
> 5 min - note well, bash - Chairs
> 15 min - status, overview - Chairs
>
> Overview of related work
> 20 min - 3GPP - Hannu Hietalahti
> 10 min - XMPP - Joe Hildebrand
>
> Requirements discussion
> 20 min - draft-ietf-atoca-requirements - Hannes Tschofenig
> 20 min - draft-ietf-atoca-cap - Hannes Tschofenig
>
> --Martin
> _______________________________________________
> earlywarning mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/earlywarning

From: "Thomson, Martin" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Wed, 10 Nov 2010 08:03:58 +0800
Accept-Language: en-US
acceptlanguage: en-US
Subject: [Atoca] Agenda update