From nobody Wed Feb 26 16:05:13 2020 Return-Path: X-Original-To: uri-review@ietfa.amsl.com Delivered-To: uri-review@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3AF3A0C1F for ; Wed, 26 Feb 2020 16:05:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.798 X-Spam-Level: X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, SPF_NONE=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFVr9mnjGv41 for ; Wed, 26 Feb 2020 16:05:11 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31A093A0C17 for ; Wed, 26 Feb 2020 16:05:11 -0800 (PST) Received: from oxusgaltgw01.schlund.de ([10.72.72.47]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Lh4nx-1jixaD2Ixr-00oVS7 for ; Thu, 27 Feb 2020 01:05:10 +0100 Date: Wed, 26 Feb 2020 19:05:10 -0500 (EST) From: Timothy Mcsweeney Reply-To: Timothy Mcsweeney To: uri-review@ietf.org Message-ID: <1404861506.56788.1582761910043@email.ionos.com> MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.1-Rev27 X-Originating-Client: open-xchange-appsuite X-Provags-ID: V03:K1:R8tbpA1KijfRij2cO4F0kUt5wTqEv3X+x7FC3S1AtW6CHEbFsVK ooSST9ssCGE8lt98qHZeMO+CSONxUuQehiTZM0yNFvntvJPki1mTIBkIuTy3sw3te1Efr8B InAcxhCda9op5YDe/S/edprqhB2lyvu/3U2681X1WEoj+T6fU4iicGToCMyeaeKQU+3jdZs gPKgeJ0ZdR7vIynxx/RJg== X-UI-Out-Filterresults: notjunk:1;V03:K0:xQO3iKgkbJM=:S72HlQ6cJlsNGXjls9UMBT UC1KNtk2SMJrCKQ4w52ecxNTEAf3XNYppmMOmpx7hXyXOU+ZQ6aSNbHQ5wJdRItJVnOX2E6JW 7aRPUm6Pkav2ltxyCZ/LJK02/ICnqzs96pDgxywUNxF6l4LKxVy3YpDQAenHxOXzvBsVve8w5 idlp4jouzZyTzmKhEYXxfIapP46TxRDmpRX2lD6esDfKPdhnJCV8upp9Fw2YuP9zz1x6iVlZV /vjvQASwLFaZtHz7lb5a68z4vSS71dR2/LCZdFFiCW3ouzwI4VVFPo+lYb4ApzbWnNeye/tvb bzmiB4jp72BRAkqrAiK86hQS48gsDwFmBPZd/UyZEBbPmNl8ElZMTaAh5GK51LdZEdGnULuOY o0BDdRH2ho5Mm30coG4JB2XDW549tNOXA7QJACoMj5JyOMfQF2vEEJEiAkltVsjeOR4DQXmIq T6unv9Hi+4mMb9q7H2mZhe8K+7p0dmC1om2TKBkOz8UtAxxJSUPPWVYiWGQCPzhASmXG0w748 efTEtlW4vC0uJwDp7q/6Jzoi8D9UHBjQHOqflZ6QrUyGjOYg2aHnyJRjP7c/QiHsdW5nNZfM+ /zg57qJPHk2Ni3mTtDMxvtm645OdZueEE2gsQkKb6K5iZGTWYPNwNF5QYz7WXcLXX2MCrOf4V 22/DqjG7SK16p4I3jRQXqY/DhpFbcXvO7IEYvqhhOwx9d/CoL+PWwZ1qqHmsOqzVIeBVzvBXw EhfPYmibIh8Z3Y3lvPM9BuE+tYCoZ3qekY1YBO6NhjJ+Ro5uzugu6vRTx1a6/v73ReNFU/HtQ JySVuRNyJGfX7fw9oMuzdPXM8ONGEIBLregyapVKIqqPiKLOMswMH3hR3GLbPwNyPPZIGLy Archived-At: Subject: [Uri-review] URI resolution questions X-BeenThere: uri-review@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proposed URI Schemes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 00:05:12 -0000
Hello All,
It was generously suggested that I may get some questions answered here about URI resolution so here it goes:

If I have a scheme name and a string like "example:123456" and the the string will be used for further processing by a second NAPTR , would I want to use the I2Rs mnemonic with a "p" flag in the first NAPTR? 

 And in this scenario, if the answer to the query of the second NAPTR is terminal , does the answer go back to where the first query originated from?

What happens to the string during the resolution process?  

I have been trying to set up a test environment for this but have not yet been successful so any tips/tricks, or tools would be greatly appreciated.

Tim
From nobody Wed Feb 26 17:41:25 2020 Return-Path: X-Original-To: uri-review@ietfa.amsl.com Delivered-To: uri-review@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87673A0DAA for ; Wed, 26 Feb 2020 17:41:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.497 X-Spam-Level: X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5zIRr8uLSRq for ; Wed, 26 Feb 2020 17:41:22 -0800 (PST) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F13573A0BE3 for ; Wed, 26 Feb 2020 17:41:21 -0800 (PST) Received: by mail-pg1-x533.google.com with SMTP id a14so552766pgb.11 for ; Wed, 26 Feb 2020 17:41:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-language:thread-index; bh=kw7jVza78AaCGnYX3pkrUT/tdu1avK0x2+CQ66P5Sf4=; b=fl4gYbS2psaUKtvYT9KABFiroT4ztWWT/8UfrVD70bWCmpUDX22R8mOT78SBmLMY3E lvLktdYkquaSi2TOy7QOm8yRzOhCKTUflJA9IRJw6b+0lxgs54rzVDIukLEsOuW6eTS+ 09EBKfB4r6RaQ9YbuvKjqQ6/1QBLyTezSFGwQkGHNTj+ng4aUPO6CxObnTXJxTaChWhL 0EHrDo6UV2eSShP2hC6SVMKUhZgKekh6t4TYV3wdoDZwXC9oVFt4QOaleJmFuxsCeX+Z gmAg2cGYvv92G86IkmLF8baoJJKb5COJ0iZqH5v6mNlqMpvyb8Z+uPXA4FF9ThggE/j8 sSpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:references:in-reply-to:subject :date:message-id:mime-version:content-language:thread-index; bh=kw7jVza78AaCGnYX3pkrUT/tdu1avK0x2+CQ66P5Sf4=; b=TL7Xyg5sRJw66a1xWUpK2IhLyQ5JK7I+s+phna0iy6/qiaHyeFWGWum9pjmEUP18y4 W7qbxZmvkda7YLPL7iTTMYwskdVogmDWe1Af3lEamsHc96JqO6ivR/k1WQRrnmkA3nlP BbPv+OeqHLL7AX0si9VV+cVnRhzDdMpkwj3GbjbSXjBUsWhS8nBDE9geQNkCf8CwhMyi xe9gZyAQwrtAuxzDQfcseU83Y3PvmBMvfHbCYGncHefuA2QSBEfxOc5tiuS+KecxiJHy j7sGc71D+YDBnNy71nzuWQbxWOLn/fy4zgjzScqQRerQAT/ODTZRLPUAP46Gz9iYUAUt xTrg== X-Gm-Message-State: APjAAAV/cN6B6Y2u/eh0Ef5sHU3SCYYpzyvfs9sYsi9J7ecPzh4X8llw aH/l6MDInM5QGfdwZ3vfXXHo1oMn X-Google-Smtp-Source: APXvYqzivqpL4VVTePAVWK9/mP09j7Gq13x9YXS9ygbZaRsgwqiTDSjT6nxLO0TzwI4jmoQe5ZFAiA== X-Received: by 2002:aa7:9ec9:: with SMTP id r9mr1602181pfq.85.1582767681205; Wed, 26 Feb 2020 17:41:21 -0800 (PST) Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id c188sm4497692pfb.151.2020.02.26.17.41.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Feb 2020 17:41:20 -0800 (PST) Sender: Larry Masinter From: Larry Masinter X-Google-Original-From: "Larry Masinter" To: "'Timothy Mcsweeney'" , References: <1404861506.56788.1582761910043@email.ionos.com> In-Reply-To: <1404861506.56788.1582761910043@email.ionos.com> Date: Wed, 26 Feb 2020 17:41:19 -0800 Message-ID: <01a901d5ed0f$02d8e980$088abc80$@acm.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AA_01D5ECCB.F4B5F7A0" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQIrpoFcKntCSB6gSAJ6KnXR+vWz56eC0DLg Archived-At: Subject: Re: [Uri-review] URI resolution questions X-BeenThere: uri-review@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proposed URI Schemes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 01:41:24 -0000 This is a multipart message in MIME format. ------=_NextPart_000_01AA_01D5ECCB.F4B5F7A0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Uh=E2=80=A6 I can=E2=80=99t make sense of your question =20 From: Uri-review On Behalf Of Timothy = Mcsweeney Sent: Wednesday, February 26, 2020 4:05 PM To: uri-review@ietf.org Subject: [Uri-review] URI resolution questions =20 Hello All,=20 It was generously suggested that I may get some questions answered here = about URI resolution so here it goes:=20 =20 If I have a scheme name and a string like "example:123456" and the the = string will be used for further processing by a second NAPTR , would I = want to use the I2Rs mnemonic with a "p" flag in the first NAPTR? =20 =20 And in this scenario, if the answer to the query of the second NAPTR is = terminal , does the answer go back to where the first query originated = from?=20 =20 What happens to the string during the resolution process? =20 =20 I have been trying to set up a test environment for this but have not = yet been successful so any tips/tricks, or tools would be greatly = appreciated.=20 =20 Tim=20 ------=_NextPart_000_01AA_01D5ECCB.F4B5F7A0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Uh=E2=80=A6 I can=E2=80=99t make sense of your = question

 

From: = Uri-review <uri-review-bounces@ietf.org> On Behalf Of = Timothy Mcsweeney
Sent: Wednesday, February 26, 2020 4:05 = PM
To: uri-review@ietf.org
Subject: [Uri-review] URI = resolution questions

 

Hello = All,

It was generously = suggested that I may get some questions answered here about URI = resolution so here it goes:

 

If I have a scheme name and a string like = "example:123456" and the the string will be used for further = processing by a second NAPTR , would I want to use the I2Rs mnemonic = with a "p" flag in the first NAPTR?  =

 

 And in this scenario, if the answer to the query = of the second NAPTR is terminal , does the answer go back to where the = first query originated from?

 

What happens to the string during the resolution = process?  

 

I = have been trying to set up a test environment for this but have not yet = been successful so any tips/tricks, or tools would be greatly = appreciated.

 

Tim

------=_NextPart_000_01AA_01D5ECCB.F4B5F7A0-- From nobody Thu Feb 27 09:09:50 2020 Return-Path: X-Original-To: uri-review@ietfa.amsl.com Delivered-To: uri-review@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94A23A0D0B for ; Thu, 27 Feb 2020 09:09:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.797 X-Spam-Level: X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5S3CHrpN9JC7 for ; Thu, 27 Feb 2020 09:09:40 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BB543A0D3B for ; Thu, 27 Feb 2020 09:09:40 -0800 (PST) Received: from oxusgaltgw10.schlund.de ([10.72.72.56]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0M4q55-1jLASK0sGb-00yz06; Thu, 27 Feb 2020 18:09:37 +0100 Date: Thu, 27 Feb 2020 12:09:36 -0500 (EST) From: Timothy Mcsweeney Reply-To: Timothy Mcsweeney To: Larry Masinter , uri-review@ietf.org Message-ID: <1285517896.32083.1582823376975@email.ionos.com> In-Reply-To: <01a901d5ed0f$02d8e980$088abc80$@acm.org> References: <1404861506.56788.1582761910043@email.ionos.com> <01a901d5ed0f$02d8e980$088abc80$@acm.org> MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 Importance: Normal X-Originating-Client: open-xchange-appsuite X-Mailer: Open-Xchange Mailer v7.10.1-Rev27 X-Provags-ID: V03:K1:d14+B9GPXp5jEeuTQBkj2jbqKTTcHuEWLyEApp0wb5PAAdQ76XK mhLUVZSNyRNxxpLM+U1flRq9wRqys+T7hb2ekunn0j0cYmsJbwprQ1PXiO1/zR1fBHCGSDh EYFT5POLerq2GfObrfQnfut2VkTFgJXssGdyMowL+7DLsZ7QnsJwTPxHM8MDy6hDO/otnDn OpAkpJKy0EpEWV9YYIRXw== X-UI-Out-Filterresults: notjunk:1;V03:K0:q3cEGz2KGGQ=:PSp1YayBYzwcm0+FjZP7yf U5M69anavkqzaNz+IgR+T7Ts18p8mwBpjhO+22mJ9UzpYQQ7gWsb0IQiRL7x5GqFh4zkC1+ir gAm9726RQ5jj11auv9fig2g6juXQfcrG/JNjOMete87DkoIzpDYuALTkDXuGIDx5NDSpfhOgA dViEaWImV4A+MuOfJ3icV1TBWo+QvY4ACJckDA068JEatNeDyhj2N1oYp9Wh/q3Jfh2CGfpXh VGSfieonO+g817oVTtR8MGMFUIAj5aQ9mmaJjMNcxZxo9+cS9ouC2CKDCYCWiDbSgHwThB9dW r7OzCT9MjXXtDWt36hM3IQrcuoj/a57QOE4fCaD9+BFrL1PKK3rkUl0byQyK0ERZE7jYfdJR3 th/7xZoINfE8g0FciMTAlo76WLAuqK3WA0Bz7NXrHtlTHZ79ND1u3HrDoqMi5l19qGQ3JogBf d8AqRV9Tvk823m23vVSoXfdpvhW2v9Ite9PLGBOIDPD9XWbbUMpRWgeNZwsdeXQzTnuDT5UVO vNNN0eXNnA1u8ATie0n1QFfJX7n3gxrT5sOZp028axTgDZ+j5AYqk40Q3vvYlYMTRHZr38Zqs OBRKRRN3sH85VFJlSmjcvJzcQbaKLRMDVXiMUjTShQzIEKWEdS/o7EL20OXPfaFdwDsVyLGdm 4LVRXOqDZ00tUDfYSivQAE9GemwDvb3d81zA28JBcDu87kxH+kNuJqeXMHs9Gv7r+AgXmyCRm yQU1ma+ZdgcX8uMOLtztsqzVsB1TSEJ+ViNu8/C6JphJ9W1u/UzfLgSRD2qhP2aVRMsgX0JhR oc2t2nm31bH3adN7+WoWyvc/5iZjmEojiEU9+8Q42ISOCYU+5vi/5OCxPyHepSRcscCgkVa Archived-At: Subject: Re: [Uri-review] URI resolution questions X-BeenThere: uri-review@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proposed URI Schemes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 17:09:48 -0000 =20 =20
Hi Larry, 

If "example:123456" is my application unique string (RFC 3402 section 3)= and the first well known rule is applied, the output being the key example= .uri.arpa.  At this point what has happened to the "123456"?  &nb= sp;I am assuming that at this point nothing has happened to the "123456" be= cause the DDDS application is now asking for rules to apply which are locat= ed in the NAPTR record at example.uri.arpa....is that correct? 
On February 26, 2020 at 8:41 PM Larry Masinter <LMM@acm.org> wrote= :=20

Uh=E2= =80=A6 I can=E2=80=99t make sense of your question


From: Uri-review <uri-review-bounces@ietf.org> = On Behalf Of Timothy Mcsweeney
Sent: Wednesday= , February 26, 2020 4:05 PM
To: uri-review@ietf.org
= Subject: [Uri-review] URI resolution questions


<= /p>

Hell= o All,

It w= as generously suggested that I may get some questions answered here about U= RI resolution so here it goes:


=

If I= have a scheme name and a string like "example:123456" and the the string w= ill be used for further processing by a second NAPTR , would I want to use = the I2Rs mnemonic with a "p" flag in the first NAPTR? 


=

&nbs= p;And in this scenario, if the answer to the query of the second NAPTR is t= erminal , does the answer go back to where the first query originated from?=


=

What= happens to the string during the resolution process?  


=

I ha= ve been trying to set up a test environment for this but have not yet been = successful so any tips/tricks, or tools would be greatly appreciated.


=

Tim<= /p>


 
=20