From nobody Sun Oct 16 10:26:39 2022 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 468F1C14F722 for ; Sun, 16 Oct 2022 10:26:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cw6aSMaDbFfw for ; Sun, 16 Oct 2022 10:26:33 -0700 (PDT) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9393C14F693 for ; Sun, 16 Oct 2022 10:26:33 -0700 (PDT) Received: by mail-io1-xd2e.google.com with SMTP id r142so7487070iod.11 for ; Sun, 16 Oct 2022 10:26:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=m0h0+dLYYaAp8XeV2jKocAKo29AVhBCDZ7rjmBpyB7k=; b=i+qXfYZEVkjhwtc8EKGG8Hl9GX0XNcGpNyLQr+NyoPMjgS8UvTVh9t0HbN5X1wvqcc zGrTorPnU2sSbw0fdAMPJKPpafjt0q0RIv1Eto2bM8hBKdGdmNYFEf2UZB4T5O+5eLhf meK+IAPTZzKFiMFGjf7AhYffa4PlYrFMeSPvMDYeE9yOsL6+zVnQ9oYO8CiLnFqA9qbb tkOaC1L9Cs7ek19aZP8X2+2fI7LZdhy6SYp/NXJ8d9biYJfrp+/yObpQPfwPrWC5oFjj wPCaOtYmqCoIXhNUzIk6PkwRLsaW5jERy5FhgWuiKlNHFNTg1rlGvDqJDRWlqBKyASux qGBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=m0h0+dLYYaAp8XeV2jKocAKo29AVhBCDZ7rjmBpyB7k=; b=BaTI2t2RcoTPV/6teXyD1UiU0JAiphei50jbdyqHYqR96UBYN3mYUndahxXcMUxPFn hprHp4JVJxCGei1ZN4YUUUgQz2oNiCmIit4CZSOGLmd/kJDVBH6avCFn1jHDTYmCFGYl R+H8Vajamy2lAFjHIh6W10QmeBK1AFhrq3mMwOpizxRfN+GSPq9lzD9T3zXbPE2CiGcO Lj0/WkJRIvTZaFF9yDCtzRgJ4Ck4I93ncLJqUBEDs1T81ZgO2qIIajZ4TtOsNoZvYVW9 POpdd+OnsFpxVW2b7N+SGhKZ44mAb82pnTynXANiY4orLmfjtXM+h3AvFGYoDJaFcnGH eZmw== X-Gm-Message-State: ACrzQf3uFBQfY7tmK+4Vp9kpbvo4gpkHAdXppBBsHsx79YZ5hBB4ODoj RGfHHsqGZBCHtoM18lFfjhMvhgSZ3zmI8DqiyyVnLU4DMMA= X-Google-Smtp-Source: AMsMyM7ThQeAzqrrbjoo0g47PfPaAj0vrR39msD/8eBd/oXwvmxmBkzAhm6NQa4QNHeIZixZXW0h19yS4r/XZSleqkI= X-Received: by 2002:a05:6638:dd6:b0:363:f22b:e969 with SMTP id m22-20020a0566380dd600b00363f22be969mr3750489jaj.148.1665941192710; Sun, 16 Oct 2022 10:26:32 -0700 (PDT) MIME-Version: 1.0 References: <20221015195315.GA11346@openfortress.nl> <20221016065327.GA12615@openfortress.nl> In-Reply-To: <20221016065327.GA12615@openfortress.nl> From: Eric Rescorla Date: Sun, 16 Oct 2022 10:25:56 -0700 Message-ID: To: dispatch@ietf.org Content-Type: multipart/alternative; boundary="00000000000002318d05eb2a2951" Archived-At: Subject: Re: [dispatch] SASL Authentication for SIP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2022 17:26:38 -0000 --00000000000002318d05eb2a2951 Content-Type: text/plain; charset="UTF-8" On Sat, Oct 15, 2022 at 11:53 PM Rick van Rein wrote: > Hello Eric, > > > As a preliminary question: do we have some expressions of interest from > > SIP-based communications providers in this mechanism? > > Not yet. This is new work, has not been implemented. The intention is to > allow calls between domains. > I'm not really following this. Users authenticate to domains with passwords (at least sometimes) but I would expect inter-domain authentication to be done with TLS mutual auth. Also, my sense is that authentication is not the primary barrier to inter-domain calling. Similar work for HTTP has been warmly welcomed by several people. > > Are you suggesting to hold back presenting in Dialog until (...)? > More or less. It's hard to see the IETF doing successful work in this space if providers aren't interested. -Ekr > -Rick > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --00000000000002318d05eb2a2951 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Oct 15, 2022 at 11:53 PM Rick= van Rein <rick@openfortress.nl<= /a>> wrote:
H= ello Eric,

> As a preliminary question: do we have some expressions of interest fro= m
> SIP-based communications providers in this mechanism?

Not yet.=C2=A0 This is new work, has not been implemented.=C2=A0 The intent= ion is to
allow calls between domains.



Similar work for HTTP has been warmly welcomed by several people.

Are you suggesting to hold back presenting in Dialog until (...)?

More or less. It's hard to see the IETF doin= g successful work in this space if providers aren't interested.



-Rick

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
--00000000000002318d05eb2a2951--