Re: [P2PSIP] UNSAF considerations and draft-ietf-p2psip-drr

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 12 July 2013 11:29 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA1611E80F9 for <p2psip@ietfa.amsl.com>; Fri, 12 Jul 2013 04:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.792
X-Spam-Level:
X-Spam-Status: No, score=-105.792 tagged_above=-999 required=5 tests=[AWL=0.457, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFpnjNIExCYX for <p2psip@ietfa.amsl.com>; Fri, 12 Jul 2013 04:29:42 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id AAEE311E80F8 for <p2psip@ietf.org>; Fri, 12 Jul 2013 04:29:39 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f586d000001a55-2e-51dfe8a2a568
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 05.FE.06741.2A8EFD15; Fri, 12 Jul 2013 13:29:38 +0200 (CEST)
Received: from [131.160.126.94] (153.88.183.146) by smtp.internal.ericsson.com (153.88.183.35) with Microsoft SMTP Server id 14.2.328.9; Fri, 12 Jul 2013 13:29:37 +0200
Message-ID: <51DFE8A1.50604@ericsson.com>
Date: Fri, 12 Jul 2013 14:29:37 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <51BEFAC4.3050302@ericsson.com> <004b01ce7026$55930650$00b912f0$@gmail.com> <51C7FF29.9070901@ericsson.com> <008401ce70b8$fd5ff220$f81fd660$@gmail.com> <51C81A7C.7030404@ericsson.com> <00c201ce7ed2$7da2b450$78e81cf0$@gmail.com>
In-Reply-To: <00c201ce7ed2$7da2b450$78e81cf0$@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnluLIzCtJLcpLzFFi42KZGfG3VnfRi/uBBif2i1ssuXmG0eJvO7MD k8fOWXfZPZYs+ckUwBTFZZOSmpNZllqkb5fAlfH6wgu2gr8WFa33brI0MP7Q7WLk5JAQMJHo fX+WDcIWk7hwbz2QzcUhJHCYUeLE/TNMEM4aRonLnxawgFTxCmhKTP2/mRXEZhFQlTi1eTNY N5uAhcSWW/fBakQFoiRae6cyQ9QLSpyc+QQsLiKgJvF67Wegeg4OZgFtiUeffUHCwgIuEpuO /gErFxJ4zyjR1ZALYnMCjWx++4wV4jhJiS0v2tlBbGYBPYkpV1sYIWx5ie1v50D1akssf9bC MoFRaBaSzbOQtMxC0rKAkXkVI3tuYmZOernhJkZgoB7c8lt3B+OpcyKHGKU5WJTEeTfpnQkU EkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwKj5KcB51h2xuxOiFzx//FS99aHQjBVe07sdGk9m P1fbxlsQs0o5ecbntal/ty/vWforNIiV5+AP64Usj/P33/8m5DCz8arkkZp1eco8eZdjovzj Jn0u7tGf0X9rh/+RpT80KpgUFO0lz2z6dVPEWeBH23qLvo0XLX7mrRd8LOEkr/zqUyP70jNK LMUZiYZazEXFiQAkPJhBIgIAAA==
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] UNSAF considerations and draft-ietf-p2psip-drr
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2013 11:29:47 -0000

Hi Roni,

sure, please go ahead work within the WG on this change and let me know
when the draft is ready.

Cheers,

Gonzalo

On 12/07/2013 10:36 AM, Roni Even wrote:
> Hi,
> After further review we will also add to the configuration document a new
> element that will specify the usage of DRR or RPR.
> I assume this is a bigger change and may require the WG to look at it
> Roni
> 
>> -----Original Message-----
>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>> Sent: 09 July, 2013 2:06 PM
>> To: 'Gonzalo Camarillo'
>> Cc: 'P2PSIP Mailing List'
>> Subject: RE: [P2PSIP] UNSAF considerations and draft-ietf-p2psip-drr
>>
>> Hi Gonzalo,
>> I will try to summarize what is the current recommendation in the document
>> and try to make  it clearer.
>>
>> 1. DRR is always available with a fall back to SRR.
>> 2. Section 6.2  of the base draft says " An overlay MAY be configured to
> use
>> alternative routing algorithms, and alternative routing algorithms
>>    MAY be selected on a per-message basis.  I.e., a node in an overlay
> which
>> supports SRR and some other routing algorithm called XXX might
>>    use SRR some of the time and XXX some of the time."  This is the
> preferred
>> way when trying to use DRR based on the overlay configuration and having
>> DRR as preferred mode.
>> 3. The administrator when defining the configuration and not having enough
>> knowledge (this is not a managed / private network) about the usage of DRR
>> but still likes to try it may configure DRR. The sender may try using DRR
> but
>> fall back to SRR if fails as explained in section 6.4 of DRR draft.
>>
>> 4. section 4.2 provides guidance about how to decide of to continue using
>> DRR or just use SRR for all cases. Still the decision to try DRR in the
> first place
>> will be based on configuration.
>>
>> 5. We can add text that say that we discourage using DRR in the open
>> Internet or if the administrator does not feel he have enough information
>> about the overlay network topology.
>>
>> 6. The application should use the configuration to decide if to try DRR
> before
>> SRR and fall back to SRR if fails
>>
>> 7. using DRR  by a node is not recommended per specific connection. The
>> application should use DRR based on success rate and should give up DRR if
>> the success rate falls for all it connections.
>>
>> 8. The  document will emphasis that the decision to continue with DRR is
> not
>> per a specific case but based on the node total success rate.
>>
>> Roni
>>
>>
>>
>>> -----Original Message-----
>>> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
>>> Sent: 24 June, 2013 1:08 PM
>>> To: Roni Even
>>> Cc: 'P2PSIP Mailing List'
>>> Subject: Re: [P2PSIP] UNSAF considerations and draft-ietf-p2psip-drr
>>>
>>> Hi Roni,
>>>
>>> sure, the purpose of this document is not to create a new ICE type of
>>> mechanism, I agree. Nevertheless, the document needs to be clear about
>>> the options implementers and administrators have. That is, what is
>>> likely to work, what is not likely to work, special cases (e.g., when
>>> two nodes are in the same private address space), etc. That is the
>>> type of (brief) discussion I would like to see in the draft. When it
>>> comes to the definition of the mechanisms themselves, I am OK with them
>> as they are.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>> On 24/06/2013 11:58 AM, Roni Even wrote:
>>>> Hi Gonzalo,
>>>> During the WG discussion we were asked to have in the main body just
>>>> the case of manage networks and leave in the informational appendix
>>>> A some informational text about finding routable addresses since it
>>>> was clear that there is no guarantee that it will work. I do not
>>>> think that it is the purpose of this document to discuss the whole
>>>> topic of finding routable addresses, we are just pointing at available
>> options.
>>>> The idea is that there is always a fall back to SRR Roni
>>>>
>>>>> -----Original Message-----
>>>>> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
>>>>> Sent: 24 June, 2013 11:11 AM
>>>>> To: Roni Even
>>>>> Cc: 'P2PSIP Mailing List'
>>>>> Subject: Re: [P2PSIP] UNSAF considerations and
>>>>> draft-ietf-p2psip-drr
>>>>>
>>>>> Hi Roni,
>>>>>
>>>>> I think the draft should discuss in more detail how a node makes
>>>>> the
>>>> decision
>>>>> of attempting to use DRR and what are the trade-offs. The case of
>>>>> closed
>>>> or
>>>>> managed networks is clear. The draft can mention that an
>>>>> administrator simply configures nodes to use DRR because the
>>>>> administrator knows, somehow, that it will work fine.
>>>>>
>>>>> In open networks, the draft should discuss the trial and error
>>>>> system
>>>> being
>>>>> proposed. For example, a node without a public IP address may be
>>>>> able to communicate directly with a node in the same non-public
>>>>> address
>>> space.
>>>>> That case is not covered by the discussions about UNSAF mechanisms.
>>>>> The whole point about developing ICE was that UNSAF mechanisms do
>>> not
>>>>> work in many situations.
>>>>>
>>>>> In short, this is an important interoperability issue because it
>>>>> relates
>>>> to when
>>>>> a node should use one mechanism or another. Therefore, the draft
>>>>> should discuss all the implications of the proposed mechanism
> carefully.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Gonzalo
>>>>>
>>>>>
>>>>>
>>>>> On 23/06/2013 6:28 PM, Roni Even wrote:
>>>>>> Hi Gonzalo,
>>>>>> Thanks for point out to RFC3424.
>>>>>> How about adding to the following sentence an informative
>>>>>> reference to RFC3424. Note that appendix A is not creating an
>>>>>> UNSAF proposal but just mentions some methods for informational
>> purpose.
>>>>>>
>>>>>> Suggest adding to "Note that there is no foolproof way to
>>>>>> determine if a peer is publically reachable, other than via
>>>>>> out-of-band mechanisms."  to
>>>>>>
>>>>>> "Note that there is no foolproof way to determine if a peer is
>>>>>> publically reachable, other than via out-of-band mechanisms. For
>>>>>> discussion about issues with address evaluation also see UNSAF
>>>> [RFC3424]"
>>>>>>
>>>>>> I am not sure if it adds much information but it may be good to
>>>>>> have this reference
>>>>>>
>>>>>> Roni Even
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org]
>> On
>>>>>>> Behalf Of Gonzalo Camarillo
>>>>>>> Sent: 17 June, 2013 3:02 PM
>>>>>>> To: P2PSIP Mailing List
>>>>>>> Subject: [P2PSIP] UNSAF considerations and draft-ietf-p2psip-drr
>>>>>>>
>>>>>>> Folks,
>>>>>>>
>>>>>>> Appendix A of the following draft describes how a node can obtain
>>>>>>> IP addresses on which it may be reached:
>>>>>>>
>>>>>>> http://tools.ietf.org/html/draft-ietf-p2psip-drr-07#appendix-A
>>>>>>>
>>>>>>> Have you taken into account the UNSAF considerations?
>>>>>>>
>>>>>>> http://tools.ietf.org/html/rfc3424
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Gonzalo
>>>>>>> _______________________________________________
>>>>>>> P2PSIP mailing list
>>>>>>> P2PSIP@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/p2psip
>>>>>>
>>>>
>