From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 741CEC0051 for ; Sun, 16 Aug 2020 17:24:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 633A2876CF for ; Sun, 16 Aug 2020 17:24:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VaoSvfzlVob for ; Sun, 16 Aug 2020 17:24:23 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by whitealder.osuosl.org (Postfix) with ESMTPS id 7EAF3876A4 for ; Sun, 16 Aug 2020 17:24:23 +0000 (UTC) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07GHOLeM032234 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 16 Aug 2020 13:24:22 -0400 Received: by mail-ed1-f49.google.com with SMTP id v22so10521524edy.0 for ; Sun, 16 Aug 2020 10:24:21 -0700 (PDT) X-Gm-Message-State: AOAM531izp4NTemt6tcDVJqF+zVHdgg6F75vwLt+PsBUl7dCAqyNYdHf zByT9gTzm5Q9rD0wiS9arPOJEy1PDWy2vTvpAlw= X-Google-Smtp-Source: ABdhPJxroqlrJi14rhVQus7q3oVWOtaC/h2y0VOAvbGKb31TGtadHcV5Lb5o7vWDkZaJoJrZmeF3QY43U8rjDvF/eaI= X-Received: by 2002:a05:6402:1a23:: with SMTP id be3mr11926209edb.138.1597598660811; Sun, 16 Aug 2020 10:24:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jeremy Date: Sun, 16 Aug 2020 10:24:09 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Suhas Daftuar , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000abe59b05ad01ec4d" Subject: Re: [bitcoin-dev] Generalizing feature negotiation when new p2p connections are setup X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2020 17:24:24 -0000 --000000000000abe59b05ad01ec4d Content-Type: text/plain; charset="UTF-8" Concept ack! It might be nice to include a few negotiation utility functions either in this bip or at the same time in a separate bip. An example we might want to include is a "polite disconnect", whereby a node can register that you don't want to connect in the future due to incompatibility. It also might be nice to standardize some naming convention or negotiation message type so that we don't end up with different negotiation systems. Then we can also limit the bip so that we're only defining negotiation message types as ignorable v.s. some other message type (which can also be ignored, but maybe we want to do something else in the future). This also makes it easier for old (but newer than this bip) nodes to apply some generic rules around reporting/rejecting/responding to unknown feature negotiation v.s. an untagged message which might be a negotiation or something else. --000000000000abe59b05ad01ec4d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Concept ack!=C2=A0

It might be nice to include a few negotiation utility functions eith= er in this bip or at the same time in a separate bip. An example we might w= ant to include is a "polite disconnect", whereby a node can regis= ter that you don't want to connect in the future due to incompatibility= .

It also might be nice = to standardize some naming convention or negotiation message type so that w= e don't end up with different negotiation systems. Then we can also lim= it the bip so that we're only defining negotiation message types as ign= orable v.s. some other message type (which can also be ignored, but maybe w= e want to do something else in the future).

This also makes it easier for old (but newer than this = bip) nodes to apply some generic rules around reporting/rejecting/respondin= g to unknown feature negotiation v.s. an untagged message which might be a = negotiation or something else.=C2=A0
--000000000000abe59b05ad01ec4d--