headers
Cullen Jennings | 2 Feb 2006 05:16
Picon
Favicon
Gravatar

Re: missing defintion in draft-ietf-behave-nat-udp-04

On 1/30/06 1:21 AM, "Karlheinz Wurm" <karlheinz.wurm <at> skype.net> wrote:

> Additional question: What is the roadmap to build the RFC out of this paper?

The abridged version is ... We have sent it to the IESG for review. They
look at it, sometime they ask for changes. Then they send it to the RFC
Editor and it becomes an RFC.
Permalink | Reply | 3 comments |
headers
Andy Yang | 11 Feb 2006 04:24
Picon
Favicon

TURN help !!!

Hi All,

I am new to this board but your help will be greatly appreciated.

I have a doubt regarding the two TURN clients both behind a symmetric  
NAT can communicate with each other using a TURN server. Please help me

Scenario:

A-----NAT 1------TURN SERVER-----NAT 2-----B

A: (a.a.a.a:1234)
B: (b.b.b.b:1234)
TURN Server: (x.x.x.x:3478)
NAT 1 and NAT 2 are both symmetric.

My understanding:
1. A, B will both send ALLOCATE to TURN server (x.x.x.x:3478), and  
get response. Suppose A is allocated x.x.x.x:11111, B is allocated  
x.x.x.x:22222.
2. A send SEND request to TURN server (x.x.x.x:3478), set  
REMOE_ADDRESS(b.b.b.b:1234); TURN server will use A's allocated  
address (x.x.x.x:1111) to send DATA to B (b.b.b.b.b:1234). It cannot  
go through NAT 2.
3. B send SEND request to TURN server(x.x.x.x:3478), set  
REMOTE_ADDRESS(a.a.a.a:1234); TURN server will use B's allocated  
address (x.x.x.x:2222) to send DATA to A (a.a.a.a:1234). It cannot go  
through NAT 1, either.

Is there anything wrong  here?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Justin Uberti | 11 Feb 2006 04:52
Picon
Favicon

Re: TURN help !!!

Andy,

In the simplest case, when A wants to send data to B, it will make a 
TURN send request to send to B's TURN address x.x.x.x:22222. A's TURN 
server will send this data from x.x.x.x:11111 to B at x.x.x.x:22222, 
which will be forwarded to B at b.b.b.b:1234.

In the real world, TURN will typically be used with ICE, where A will 
send to B's TURN address, B's STUN-derived address, and b.b.b.b:1234, 
and will use the best address that works.

Hope this helps,
--justin

ayang <at> apple.com wrote:

> Hi All,
>
> I am new to this board but your help will be greatly appreciated.
>
> I have a doubt regarding the two TURN clients both behind a symmetric  
> NAT can communicate with each other using a TURN server. Please help me
>
> Scenario:
>
> A-----NAT 1------TURN SERVER-----NAT 2-----B
>
> A: (a.a.a.a:1234)
> B: (b.b.b.b:1234)
> TURN Server: (x.x.x.x:3478)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Cullen Jennings | 16 Feb 2006 01:31
Picon
Favicon
Gravatar

Adoption of WG documents


The chairs and ADs are in the process of updating the charter to include the
media relay work. At the last meeting we discussed the topic of adopting the
following drafts as working group drafts:

http://www.ietf.org/internet-drafts/draft-rosenberg-midcom-turn-08.txt

http://www.ietf.org/internet-drafts/draft-camarillo-midcom-turn-ipv6-00.txt

There was strong support in the room for using these as the starting point
for this work. If anyone on the list has objections, please let us know,
otherwise I will declare consensus on adopting them. Please let us know by
February 19.

Thanks, Cullen & Jiri
Permalink | Reply | 4 comments |
headers
Internet-Drafts | 17 Feb 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-behave-multicast-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.

	Title		: IGMP Proxy Behavior
	Author(s)	: D. Wing
	Filename	: draft-ietf-behave-multicast-01.txt
	Pages		: 10
	Date		: 2006-2-17
	
This document describes the behavior of an IGMP Proxy, as implemented
in NAT devices, and places requirements on such devices.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-multicast-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-behave-multicast-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Cullen Jennings | 18 Feb 2006 02:04
Picon
Favicon
Gravatar

WGLC of draft-ietf-behave-multicast


I would like to begin working group last call of:

draft-ietf-behave-multicast-01

Please have all your comments in by March 3rd.

Thanks, Cullen & Jiri
Permalink | Reply | 0 comments |
headers
Pyda Srisuresh | 20 Feb 2006 19:52
Picon
Favicon

Re: Adoption of WG documents

Cullen,
Back in 11/05, I requested to initiate the procedure to adapt the following as WG documents and consider
adding a related draft to the milestones.
    draft-srisuresh-behave-nat-icmp-00.txt
    draft-ford-behave-app-01.txt

Both these drafts have a matching WG milestones. I havent heard anything as yet on these. It seems a bit
premature to talk about revising the chapter and milestones before addressing what is already on the WG
plate. 
If there is large support to add the items below, that is fine. However, before revising the charter and
milestones, I would suggest getting feedback from folks on what else they would like to see added to the
charter and milestones.

Thanks.

regards,
suresh 

----- Original Message ----
From: Cullen Jennings <fluffy <at> cisco.com>
To: Behave <ietf-behave <at> list.sipfoundry.org>
Sent: Wednesday, February 15, 2006 4:31:57 PM
Subject: [Ietf-behave] Adoption of WG documents

The chairs and ADs are in the process of updating the charter to include the
media relay work. At the last meeting we discussed the topic of adopting the
following drafts as working group drafts:

http://www.ietf.org/internet-drafts/draft-rosenberg-midcom-turn-08.txt
(Continue reading)

Permalink | Reply | 2 comments |
headers
Cullen Jennings | 21 Feb 2006 00:38
Picon
Favicon
Gravatar

Re: Adoption of WG documents

On 2/20/06 10:52 AM, "Pyda Srisuresh" <srisuresh <at> yahoo.com> wrote:

> Cullen,
> Back in 11/05, I requested to initiate the procedure to adapt the following as
> WG documents and consider adding a related draft to the milestones.
>     draft-srisuresh-behave-nat-icmp-00.txt
>     draft-ford-behave-app-01.txt
> 
> Both these drafts have a matching WG milestones. I havent heard anything as
> yet on these. It seems a bit premature to talk about revising the chapter and
> milestones before addressing what is already on the WG plate.
> If there is large support to add the items below, that is fine. However,
> before revising the charter and milestones, I would suggest getting feedback
> from folks on what else they would like to see added to the charter and
> milestones.
> 
> Thanks.
> 
> regards,
> suresh 

Hi, 

Few separate issues here.

On the ford-behave-app. I was sort of working on the assumption that this
had good odds of becoming a WG draft but it has had very little "air time"
or comments yet. Most the WG has not read it. This is partially because the
UDP and TCP stuff is sequenced ahead of it and the UDP took so long. I would
hope we would end up with agenda time this at the upcoming meeting.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Pyda Srisuresh | 21 Feb 2006 03:33
Picon
Favicon

Re: Adoption of WG documents


--- Cullen Jennings <fluffy <at> cisco.com> wrote:

> On 2/20/06 10:52 AM, "Pyda Srisuresh" <srisuresh <at> yahoo.com> wrote:
> 
> > Cullen,
> > Back in 11/05, I requested to initiate the procedure to adapt the following
> as
> > WG documents and consider adding a related draft to the milestones.
> >     draft-srisuresh-behave-nat-icmp-00.txt
> >     draft-ford-behave-app-01.txt
> > 
> > Both these drafts have a matching WG milestones. I havent heard anything as
> > yet on these. It seems a bit premature to talk about revising the chapter
> and
> > milestones before addressing what is already on the WG plate.
> > If there is large support to add the items below, that is fine. However,
> > before revising the charter and milestones, I would suggest getting
> feedback
> > from folks on what else they would like to see added to the charter and
> > milestones.
> > 
> > Thanks.
> > 
> > regards,
> > suresh 
> 
> Hi, 
> 
> Few separate issues here.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Cullen Jennings | 23 Feb 2006 21:34
Picon
Favicon
Gravatar

Agenda Requests


If people have requests for agenda time at the next meetings, please email
Jiri and I.

Thanks, Cullen
Permalink | Reply | 0 comments |

Gmane