Manchester City defender Nicolas Otamendi's agent has hinted his client would jump at the opportunity to play for Real Madrid.
Argentina international Otamendi's stock is still high in Spain after an impressive season at Valencia in 2014-15 before he joined City for a reported £31.5million.
The 29-year-old has not always convinced at the Etihad Stadium, however, as part of a City backline regularly lacking the calming presence of injury-prone captain Vincent Kompany, and his representative Martin Sendoa told Radio Continental Otamendi would be interested in a move back to LaLiga.
Sendoa said: "Nico is happy at Manchester City. But who wouldn't like to play at Real Madrid? It's the biggest club in the world."
Sendoa also touted Otamendi as a possible replacement at the Santiago Bernabeu for Pepe, whose contract expires at the end of the season, adding: "Pepe is leaving Real Madrid and Otamendi fits the profile they are looking for.
"Jorge Mendes [Cristiano Ronaldo's agent] is managing Otamendi in Europe.
"Barcelona have also followed him since he was at Valencia."
Of more pressing concern for Otamendi is Tuesday's Champions League last-16 first leg at home to Monaco, in which he will face former team-mate Radamel Falcao.
Falcao struggled for form and fitness during disappointing loan spells in England with Manchester United and Chelsea but has regained his predatory instincts this season to play a key role in Monaco's Ligue 1 title challenge.
Otamendi told City's official website: "He is a top player and very skilful inside the box.
"We were team-mates at Porto and we've faced each other when I’ve played against Colombia for Argentina.
"As a defender, you always have to be cautious when you play against him. Returning to Monaco was good for him and he’s scored 22 goals in 27 games, so he’s found his form again."
Get the best features, fun and footballing frolics straight to your inbox every week.
Thank you for signing up to Four Four Two. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.