Re: [dhcwg] IMEI also according rfc3315 when Board Replaced ?

"Ms. Li HUANG" <bleuoisou@gmail.com> Fri, 25 November 2022 11:22 UTC

Return-Path: <bleuoisou@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A833C14F722 for <dhcwg@ietfa.amsl.com>; Fri, 25 Nov 2022 03:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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=gmail.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 G-AYFGd_Wiwi for <dhcwg@ietfa.amsl.com>; Fri, 25 Nov 2022 03:22:00 -0800 (PST)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 1C632C14F607 for <dhcwg@ietf.org>; Fri, 25 Nov 2022 03:22:00 -0800 (PST)
Received: by mail-pj1-x1035.google.com with SMTP id k5so3447390pjo.5 for <dhcwg@ietf.org>; Fri, 25 Nov 2022 03:22:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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=El0LZQ41YZo4iLA11I1uUE/vsAYR0wH4Um9gMUZkvhQ=; b=Q90sr1fFfI7bkm9HEEMOrSYAP2vLg4mV5FegqgAsZrari6uiwcQSnYYWvWQIboKWDI crSMm8lnVYGa5EjbSWVQ+2/iJElVDfuvB1hr4we48xR1nyPDP0m8AgpBmQFFSUPyJn+h NB6pBPxOuwMkatajmNteBFEnridcPX7gy7zPdfkHAf4U4RVmkXjEwqEqRGrq6Rd+ClW1 xR0aQlHEZDvOeiyDWtPVE8nzlvi0mQRaoua47gMt0OXWrDS14hL5sEYtt9/Gt0FkwA5O fMBagQ0eBZaqNg5/tlLidd3LGIV6e1nk+/Sa1cYfNBtk8QP2A+AFKLv+WGQ6fEg0v+IO Phzw==
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=El0LZQ41YZo4iLA11I1uUE/vsAYR0wH4Um9gMUZkvhQ=; b=jtt0YhLvHIQfYokhzkuaehhCyPCDFLH+r53QoCminztZmKXfhvzJqZLa9Bc2XbJuhE JsKYeIrhO+92OGLPIWXs77REJ6w+p8hpwAc/UuYnwgpuovgtGHTh+tmzjlfpmhdzS+wz mPD/TZCGDQjqF2Vp2ImMbOMI8k6NkcGX/scgSKBYean4fjaiG8u4/6JOjk4eeItZ9Wzv lp7OAesI11dmrzxe5iseqd04AXdZqMLEi8Oy7oJJyDSm7V1ZotgXx86hFOSZ9h253/Tw WLPpkYyqUMcHHdugsKW4AcKhqkeUjQKu1vFdlfPxoW35k4gHRO5pLK/t1w7LWj/i2MCJ 53nw==
X-Gm-Message-State: ANoB5plllhpCXG6TQSxLOIdLFuDjG0oxCWYY0RFT0MruSLOKpexj098H a70Q/o+FQUoDD3NxI9XSm9IpoxDlObASCmpEN3ilSPyKBxs=
X-Google-Smtp-Source: AA0mqf6b+BJfADiOmpUZR4xk/IpuxA7NpU+W/HXNJXR/UH1+5CLuzCh2vbjkSx9nqYBFBXcCmmVT/DF+ydFlGlqka4E=
X-Received: by 2002:a17:902:f552:b0:186:b768:454d with SMTP id h18-20020a170902f55200b00186b768454dmr19870147plf.82.1669375319068; Fri, 25 Nov 2022 03:21:59 -0800 (PST)
MIME-Version: 1.0
References: <CAGGiuEY+HnON_+--xd_La97BQNm=u5B5304PJH5365r+v2152Q@mail.gmail.com>
In-Reply-To: <CAGGiuEY+HnON_+--xd_La97BQNm=u5B5304PJH5365r+v2152Q@mail.gmail.com>
From: "Ms. Li HUANG" <bleuoisou@gmail.com>
Date: Fri, 25 Nov 2022 19:21:46 +0800
Message-ID: <CAGGiuEaLGKErsmj4Kx_9zCb2aPZvNS8_vPw4RxSLEJ5vSG38Xg@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e3d2a405ee49bae0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/4tSqqNH3JrdSNZa1KQG0H7-z5dI>
Subject: Re: [dhcwg] IMEI also according rfc3315 when Board Replaced ?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Nov 2022 11:22:04 -0000

Nov 25 2022 19:20.hk S8


Thank you search DB, find
rfc7254,7255...5626,4122


Sincerely
Li

On Fri, Nov 25, 2022, 08:51 Ms. Li HUANG <bleuoisou@gmail.com> wrote:

> Nov. 25 2022  20:50.hk w10pro.m920t.FO76QM5 m.sg(pri).rv(v6 cf)- & wr, mx
>
>
> Good day ,
>
>
> IMEI also according to rfc3315 which began from the desktop, when Board
> Replaced?
>
> Wireless truly running too much faster over the wire network, from 5G , 6G
> testing recently found and,  shocked to see that, a brand remain center
> like to have the client cellphone board to do test or else ...? Google rsc
> has said, IMEI can change, another expert told IMEI supposed never changing
> ...
>
>
> How to identify this device without a permission board replaced ?
> - Its supporter chat using old x2 IMEI(s)
> - 6 months of 2-year-warranty, not responding adaptly solution when
> device is locked, (takes 2          months to solve if a client would like
> to put the device there ?!)
>
>
> Beyond RFC3315, some RFC specific rules on IMEI management please ?
>
>
> Best Regards
> BleuOisou@gmail.com
>