Re: [IPv6] Architectural comments on draft-ietf-6man-ipv6-over-wireless-

Michael Sweet <msweet@msweet.org> Fri, 28 July 2023 11:59 UTC

Return-Path: <msweet@msweet.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FDBAC15199E for <ipv6@ietfa.amsl.com>; Fri, 28 Jul 2023 04:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=msweet.org
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 jn-vEF2jBHyw for <ipv6@ietfa.amsl.com>; Fri, 28 Jul 2023 04:59:53 -0700 (PDT)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F16A6C137377 for <ipv6@ietf.org>; Fri, 28 Jul 2023 04:59:53 -0700 (PDT)
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.msweet.org (Postfix) with ESMTPSA id 1859680438; Fri, 28 Jul 2023 11:59:52 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 1859680438
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1690545593; bh=SU44V2zBCZURtf3G03YrWr3rq0y9xF7zgrmFjG/yFYw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=LHxDlaMmUuRXqTtUbHunQjjhIugEmmfmmDA9z21LjcFYyMd9z3+t5CD3OGJpRkygy Gn6+wCRILCw3yCTNBh8yN0B+GU5YmrpSpDTZ1u3jice9Aijek4s1n9v1JpVqaUOFqn g+B88fUl0Z1Zu38iYeFhZnKQaItBhPb2fJEpsP6Q=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Michael Sweet <msweet@msweet.org>
In-Reply-To: <9728BA13-FE88-478D-B44F-6D9A4DDAA67F@cisco.com>
Date: Fri, 28 Jul 2023 07:59:41 -0400
Cc: Ted Lemon <mellon@fugue.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A94E320-5495-4CEF-965A-D89FBD3972A0@msweet.org>
References: <CAKD1Yr1piLMJEh_hqpBi1a559qKD41B7Pb4Fi2U0aPEMSosNTw@mail.gmail.com> <CAPt1N1nAedaCVfxD7pn+2DsA1nrXZkKYpjS_qLN8gVCMdM=NRg@mail.gmail.com> <9728BA13-FE88-478D-B44F-6D9A4DDAA67F@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Cw1xHb13wa2-LfiNXOurYmNASRY>
Subject: Re: [IPv6] Architectural comments on draft-ietf-6man-ipv6-over-wireless-
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2023 11:59:58 -0000

Pascal,

> On Jul 27, 2023, at 5:24 PM, Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
> 
> Hello Ted  
> 
> My message did not land as intended.
> The intent is this:
> 
> I have a large building or campus. I want to enter anywhere and obtain an address that I can use throughout the campus without renumbering when I go to the next building/ level/room.
> 
> Otoh I want that bonjour always finds the nearest printer and that printer is in the same room as me or in a closeby room. Certainly not anywhere in the campus.

OK, so "nearest printer" is a problem we solved for IPP over 10 years ago - almost all printers sold since 2010 support AirPrint, which means mDNS/DNS-SD + IPP, with DNS LOC records (RFC 1876) advertising their location as configured by the admin.  This information is (naturally) also available via IPP queries.  Clients can (though few do) show the closest printer to them with this information.  All of this happens far above the subnet you are on, however...

Also, in many environments you don't actually talk directly to a printer at all.  So-called "Release Printing" solutions are popular in enterprise networks and give you a single point of entry for printing - submit your job to a central queue/service, go to any printer, and then release it for printing at that printer's console (by swiping your ID badge, or by entering a PIN, or whatever). This print service is available via a routable address, so again you don't care about the subnet.

I don't think printing can be the poster child for this draft...

________________________
Michael Sweet