IETF Logo Mail Archive

Re: [Stox] core: connecting to remote domain

<Markus.Isomaki@nokia.com> Thu, 20 June 2013 10:37 UTC

Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF18021F9A5B for <stox@ietfa.amsl.com>; Thu, 20 Jun 2013 03:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.446
X-Spam-Level:
X-Spam-Status: No, score=-5.446 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 vdUVOc4PFRDR for <stox@ietfa.amsl.com>; Thu, 20 Jun 2013 03:37:08 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 73EF621F9A6C for <stox@ietf.org>; Thu, 20 Jun 2013 03:37:07 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (in-mx.nokia.com [10.160.244.30]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r5KAb4QG015514; Thu, 20 Jun 2013 13:37:04 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.49]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 20 Jun 2013 13:37:04 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.114]) by 008-AM1MMR2-015.mgdnok.nokia.com ([65.54.30.49]) with mapi id 14.02.0328.011; Thu, 20 Jun 2013 10:38:44 +0000
From: Markus.Isomaki@nokia.com
To: salvatore.loreto@ericsson.com, stox@ietf.org
Thread-Topic: [Stox] core: connecting to remote domain
Thread-Index: AQHObT1bGqwIFhVywUGThOPE2dMt4Zk+IrcAgAABpgCAAC7yAIAAFKTw
Date: Thu, 20 Jun 2013 10:37:02 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A01DB9D@008-AM1MPN1-042.mgdnok.nokia.com>
References: <51C23237.30203@stpeter.im> <1050DBB5-7660-477A-BF07-F8BE853D0DFA@ag-projects.com> <B66E77A7-ADB3-48F4-B359-8839D6EAAD64@ag-projects.com> <51C2C882.5050107@ericsson.com>
In-Reply-To: <51C2C882.5050107@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IgddHNxpFrpWmlMbp4RmRYKuRBUI8Vhn3O3//74GRyzYbejcgK0GbepKbWimPwGBXBqeaeFewt/fv6npEucp6wbuu2ISmiyf3WEO7r38oi3BLjBNlot+9Rg+T74uVVspYKy9es0u+G8UPlU72iC4CLYClidIf4Ivqun+2G1YuhRUPwos8TfDSaBE7UD32qGpjxp/5Erz3boIaV376OLpzkB+14f6YO5rZHzgyAdsZ1Q4
x-originating-ip: [172.21.81.125]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jun 2013 10:37:04.0258 (UTC) FILETIME=[1AD46620:01CE6DA2]
X-Nokia-AV: Clean
Subject: Re: [Stox] core: connecting to remote domain
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 10:37:14 -0000

Hi Sal,

Salvatore Loreto wrote:
> 
> On 6/20/13 9:28 AM, Adrian Georgescu wrote:
> > XMPP has defined DNS records for both C2S and S2S connections. One
> > domain may have a server to server XMPP capability but would not accept
> > client connections (missing correspondent  DNS record), this would give me a
> > clue that that foreign domain has such XMPP 2 SIP gateway in place and if I
> > am a client of that domain I know I cannot use an XMPP client for it.
>
> sorry but what would be the reason to have (and expose thru DNS) an
> XMPP2SIP gateway and then not let it to be accessible from a client?
> are you assuming that a XMPP2SIP gateway is always only an outbound one?
> 

I suppose it would be the case where the domain only runs a SIP service internally, and just offers an XMPP gateway to external domains. So, if you have an XMPP-only client, you would have to get an account for some other domain to be able to communicate with this SIP-only domain.

Markus

v2.23.0 | Report a Bug | By Email