From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ordex@autistici.org>
Date: Fri, 1 Mar 2013 12:48:03 +0100
From: Antonio Quartulli <ordex@autistici.org>
Message-ID: <20130301114803.GF20607@ritirata.org>
References: <CAP5XTDP_8pCJA8uXpQoMNExiVaCvmBCmkKT_aDErk0qYk7-pmw@mail.gmail.com>
 <20130301111118.GD20607@ritirata.org>
 <CAP5XTDPApa0OvO-Z3mWRFsvk=aL+No09_Ce2eUxkZp+B_rXC9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="B0nZA57HJSoPbsHY"
Content-Disposition: inline
In-Reply-To: <CAP5XTDPApa0OvO-Z3mWRFsvk=aL+No09_Ce2eUxkZp+B_rXC9g@mail.gmail.com>
Subject: Re: [B.A.T.M.A.N.] Implement DAT for IPv6
Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n@lists.open-mesh.org>
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n.lists.open-mesh.org>
List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe>
List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/>
List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org>
List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help>
List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe>
To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@lists.open-mesh.org>


--B0nZA57HJSoPbsHY
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 01, 2013 at 01:41:28PM +0200, Mihail Costea wrote:
> On 1 March 2013 13:11, Antonio Quartulli <ordex@autistici.org> wrote:
> > On Fri, Mar 01, 2013 at 12:59:18PM +0200, Mihail Costea wrote:
> >> Hi,
> >>
> >> I've started implementing DAT for IPv6 and I have a few questions
> >> regarding the design.
> >> I've already implemented a snooping mechanism for Network Solicitation
> >> package,
> >
> > I forgot to ask here: packets generated by the IPv6 the Neigh Discovery=
 Protocol
> > are sent on a periodic basis, right? so what is the idea behind the sno=
oping
> > mechanism? There is not a request (like for ARP), right? So when should=
 the data
> > in distributed table be used?
>=20
> From what I understood the Neighbor Solicitation and Neighbor
> Advertisement packets are the ARP equivalents.
> So if we receive a Neighbor Solicitation than we would use the
> distributed table and send the Neighbor Advertisement directly.

Oh ok, It was my fault. I quickly re-read part of the RFC4861: only router
advertisement are sent on a periodic basis, while the neighbour advertiseme=
nt is
asynchronously sent either on address change or as a reply to a neighbour
solicitation.

Thanks.

Cheers,

--=20
Antonio Quartulli

=2E.each of us alone is worth nothing..
Ernesto "Che" Guevara

--B0nZA57HJSoPbsHY
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBCAAGBQJRMJVzAAoJEADl0hg6qKeOB00P/iL5X/USOnL8aEfdvJuKsYQT
CTACNBrDU0q0brUUbW8micAcZdW2V8L/Vm8MxBm1GN2zUlyZZ5Ddo6Lu3gXk6hMI
oMrK1jTNRwVxvRVQJUZfnv4su3gNifLN4nenFdDeYqJzRxRWHX+YPl+HTOyavOdo
7kqHN3xlP8wQswMgZ8qT+a5OtGSuqHdHN8BCkxL1kzQuX5LMzO/QWWZffyQ8fT00
p5NRZKCvnHXfQHfciqfaeYpjiAf3UbqJU2+LedrFUED7ztB0mAfidvqjjCxetJdl
zsqJIGFg8iJGPQPaYHoABfLFoD8m7FEMlWj7b0btqzo1aaw3K7GiDQzLOz7Yl18K
fA2oSORFeWY31ZEjg7H9mKDyH1CVA1TX+fp0jvwgl67nuL6YnbHmlP6wkiYgZFwM
/xArRQZL+TDj+sG3H97k74SXWatt1C+d+Hwbx6BoWqs0Qv/cfzHFyVcGrGZUmR0m
eDzOi3R8U7JB3QkEcUq28aeCZLkWinnVyb7CAqhUblecz0TYLj3YqDRQ+y0PiH33
C/irKPnqVa3rzdjqyI9eICBTtKeP6b0uXD5aQeLcrQyJchb2v17MxCRMM53xau50
RENvvkEAKBv+uI4EXYZe70z3aA/7MCJ1iaoqrZsQxkTDLEJ0IhfbotbFtvdFigVi
2rRKGm1S94D877+7OeBi
=7xDO
-----END PGP SIGNATURE-----

--B0nZA57HJSoPbsHY--